feature(oauth2): allow passing additional form params to token endpoint #9249
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 PR adds a config variable allowing users to add arbitrary fields to the form body sent to the token endpoint.
Motivation and Context
Some OAuth2 providers, like Logto, accept additional parameters in the body of the token endpoint. For example, if you pass
resource=https://api.example.net
, it would issueaccess_token
for that particular API.I'm not yet sure if this is a valid OAuth2 implementation detail, but it should make the configuration more versatile and allow working with more identity providers.
How Has This Been Tested?
Not yet :') I'll be grateful for pointers to how to cover it with unit / integrations tests!
Checklist
My PR contains...
src/
is unmodified: changes to documentation, CI, metadata, etc.)package.json
)My changes...
Documentation
Automated tests