Add tokenParams option #497
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
The test failures does not seem related to this PR. |
Marsup
added a commit
to hapijs/.github
that referenced
this pull request
Mar 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This mirrors the
providerParamsandprofileParamsoptions, to allow custom parameters to be supplied to thetokenendpoint request.This is needed by Auth0, which cannot return a JWT token without the
endpointparameter added to both the/authorizeand/tokenrequest. More details here: https://auth0.com/docs/secure/tokens/access-tokens/get-access-tokens#control-access-token-audience.Note that the existing
providerParamsoption, seems to be confusingly named. I guessauthParamswould be better, but renaming it requires a breaking change.