poc: add get_token_on_behalf_of() to auth0-api-python#81
Open
nandan-bhat wants to merge 2 commits intomainfrom
Open
poc: add get_token_on_behalf_of() to auth0-api-python#81nandan-bhat wants to merge 2 commits intomainfrom
nandan-bhat wants to merge 2 commits intomainfrom
Conversation
This file contains hidden or 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.
Changes
Implemented
OBOtoken exchange support inauth0-api-pythonby addingApiClient.get_token_on_behalf_of(...)as a thin wrapper over the existingRFC 8693exchange flow.The new
APIkeeps the application-facing contract simple by accepting only the incoming access token, downstreamaudience, and optionalscope, while reusing the existing confidential-client authentication and token exchange behavior internally.This PR also adds the exported
OBOresult type, targeted test coverage for the new method, andREADME/examplesupdates.The change is additive and does not introduce breaking changes to the existing SDK surface.