Add an authentication service for the Microsoft OAuth2 On-Behalf-Of flow #42
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.
This PR adds a new
DfOAuthTwoOboProvidertrait, which implements the modified user authentication flow, needed to implement the Microsoft OAuth 2.0 On-Behalf-Of flow. The most important change is to thepublic function user()function, which requests an initial OAuth token, but now must request two additional access tokens through the OBO flow. One token will be used to access the target API resource, and one will be used to load the authenticated user's data from Microsoft Graph.See also, the accompanying PR in the df-azure-ad repo: dreamfactorysoftware/df-azure-ad#14