client-api: Add support for API scope restriction #1249
Merged
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
zecakeh
force-pushed
the
zecakeh/oidc-scope
branch
from
5187b54 to
5581ccb
Compare
jplatte
reviewed
Jul 27, 2022
jplatte
reviewed
Jul 28, 2022
jplatte
approved these changes
Jul 28, 2022
zecakeh
force-pushed
the
zecakeh/oidc-scope
branch
from
ad9a192 to
06647f6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
According to MSC2967.
At some point we might also add scopes, but right now it's unclear how much me need them and they might make more sense to be only defined in the OIDC/OAuth2.0 side.
Preview Removed