[SDK-1634] Pass custom options to the token endpoint #465
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.
Description
This fixes the ability to send custom options when using
getTokenSilently
in conjunction with using refresh tokens.When using custom parameters with
getTokenSilently
, these custom options are now sent to both the authorize endpoint in the query string and the token endpoint in the request body (when not using refresh tokens), and to the token endpoint only, when using refresh tokens.These custom parameters can then be picked up in a custom Rule.
This functionality appeared to work in when not using refresh tokens, as you could pass custom options and they would be sent, but only to the authorize endpoint.
References
Fixes #448
Testing
Added test coverage, also tested manually using the playground.
Checklist
master