Open
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.
Description
Adds an On-Behalf-Of (OBO) token exchange command to imscli. The "obo" command (alias "ob") exchanges a user access token for a new token using IMS token v4 and the RFC 8693 token-exchange grant type
Usage: "imscli obo -c -p -t -s "
Security: OBO tokens are for backend use only; they must not be sent to frontend clients.
Motivation and Context
To be able to test obo-exchange.
How Has This Been Tested?
Manual: run "obo" with valid client ID, secret, and user token plus "-s openid" (or other allowed scopes) and confirm a token is returned. Run without "-s" and confirm ims returns an error.
Types of changes
Checklist: