Add multiple audiences capability to JWT verification #57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Auth0Service
to allow for arrayapi_audience
valuesapi_client_id
config option to add the Client ID to theapi_audience
valueapi_identifier_array
config option to define an array of API audiences to allowThis is a non-breaking change that allows the original string definition for
jwt_auth.api_identifier
to continue working. If you just need to add the Client ID to the allowed audiences, add the newjwt_auth.api_client_id
config option like so (using.env
variables):If you instead want to define an array of audiences to use, do that like so:
Closes #54