Update docs on OnBehalfOf authentication flow #1617
Draft
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
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.
Updates guidance on on-behalf-of flow.
Previous description insinuated that an access token for Microsoft Graph could be re-used as an assertion, however this leads to an
invalid_granterror when the same token is used as theassertionin the on-behalf-of flow.On-behalf-of flow expects the initial access token issued to have an audience (
aud) claim of the intermediary API then the intermediary can exchange the assertion for a Microsoft Graph access token.This PR updates the description to reflect this better & links to various resources.
Azure Identity docs are not very clear about setting this up.
part of #1472
Microsoft Reviewers: Open in CodeFlow