This repository has been archived by the owner on Jun 12, 2021. It is now read-only.
[WiP][ProviderInfoDiscovery] Keep unknown scopes #11
Conversation
This file contains 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
…them from RP authz request
peppelinux
changed the title
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 Work in Progress PR related to this: IdentityPython/oidcendpoint#73
With this PR a RP can request unavailable/unknown scopes, independently by those reported by provider discovery informations.
OidcRP, with this PR, will hold the unknown/unavailable scopes in its authz request.
The behaviour of Authz Endpoint (OAuth2 or OIDC) would instead be based on the internal policy configured (oidcendpoint's deny_unknown_scopes).
This is an ambitious feature, which strives to bring jwtconnect py stack into a jungle of "pirated" RP / Clients not caring about the correct use of tokens (for the purposes for which they were released). This PR does not affect OP policies (as this does: IdentityPython/oidcendpoint#85) but only the behaviour of RP, in front of the provider info response.