OAuth: Fix for multiple redirect_uris
#2756
Open
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.
In the client metadata, multiple
redirect_uri
can be specified,Any value contained in the
redirect_uris
can be used in theoptions
of theOAuthClient.authorize()
method.However, even in the above case, the current implementation automatically selects and sends
this.clientMetadata.redirect_uris[0]
in the token request, so even if the redirected params are correctly obtained,exchangeCode()
returns the following error.Actually, the
callback()
method does not receive the redirect_uri, so I think the only way to get the value of theredirect_uri
used in the PAR is throughstateStore
.