This repository was archived by the owner on Jun 12, 2021. It is now read-only.
[Option] Authorization denied for unallowed scopes#85
Merged
Conversation
Contributor
|
Fine |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 PR would introduce something heavy but, in some case, useful.
Which those present some faulty RP/Client/RS where the token were not succesfully checked against the scopes for which the token was release for.
The option
deny_unknown_scopesforce the Authz endpoint (both OAuth2 and OIDC) to return ainvalid_scopeerror message, with http status 400.Configuration can be made as follow
This PR is a WiP that follows #73