-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Add On-Behalf-Of (OBO) Auth Flow for the Microsoft Graph Team #15804
Comments
.NET’s PR: Azure/azure-sdk-for-net#22146 |
Here’s the design proposals I’m proposing to the architects: https://gist.github.com/sadasant/ece98248cb8cd2df5edd03ab92749f35 @xirzec , @chradek , @bterlson , when you have the time, your feedback is appreciated. cc: @schaabs |
After discussing the designs with @xirzec , we believe the “swapping credentials” approach to be the most promising one. I will be working on a pull request. |
Update:
Based on that, I’ll move these issues to the backlog: |
The OAuth 2.0 On-Behalf-Of flow (OBO) serves the use case where an application invokes a service/web API, which in turn needs to call another service/web API. The idea is to propagate the delegated user identity and permissions through the request chain. For the middle-tier service to make authenticated requests to the downstream service, it needs to secure an access token from the Microsoft identity platform, on behalf of the user.
Related Links:
Prototype: jongio/azidext#41
Documenation: https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-on-behalf-of-flow
.NET Design: https://gist.github.com/christothes/15b9903f7da0954aee166166a8fa1919
MS Graph Team's tracking issue: microsoftgraph/msgraph-sdk-java-core#132
The text was updated successfully, but these errors were encountered: