This are keys for the various APIs. In some scenarios, a token request to an authentication endpoint requires
a specific audience that depends on the API that is being called. For example, the ZEEBE audience is used for
the Zeebe API, while the OPTIMIZE audience is used for the Optimize API.
Any implementation of IHeadersProvider will be called with one of these keys for an authorization header,
depending on which API client is requesting the header.
See the OAuthProvider implementation for an example of how this is used.
In cases where the audience is not required (such as cookie or basic authentication), it can be ignored.
This are keys for the various APIs. In some scenarios, a token request to an authentication endpoint requires a specific audience that depends on the API that is being called. For example, the
ZEEBEaudience is used for the Zeebe API, while theOPTIMIZEaudience is used for the Optimize API.Any implementation of IHeadersProvider will be called with one of these keys for an authorization header, depending on which API client is requesting the header.
See the
OAuthProviderimplementation for an example of how this is used.In cases where the audience is not required (such as cookie or basic authentication), it can be ignored.