Update scopes-oidc.md #1324
Open
Update scopes-oidc.md #1324
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
I work in Azure Entra ID support and have gotten several requests for clarity on the OIDC scopes. During a consent prompt, these scopes are not always listed in separate lines so it can appear that scopes are being added that are not consented to. I am proposing this clarification so that customers do not believe there are any sort of "bundled" permissions. I also think some clarity should be added around which tokens these scopes are for (ID or Access Tokens). But that might make things more confusing.
|
@peedywheatstraw : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 761276b: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
@omondiatieno Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
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.
I work in Azure Entra ID support and have gotten several requests for clarity on the OIDC scopes. During a consent prompt, these scopes are not always listed in separate lines so it can appear that scopes are being added that are not consented to. I am proposing this clarification so that customers do not believe there are any sort of "bundled" permissions. I also think some clarity should be added around which tokens these scopes are for (ID or Access Tokens). But that might make things more confusing.