feat: resource parameter#60
Merged
Merged
Conversation
feat: obo
feat: Add optional IMS Org parameter for client credentials flow (adobe#57)
telegrapher
approved these changes
Apr 16, 2026
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
2 participants
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
Added RFC 8707 "resource" parameter support to "ims-go" library, enabling audience-restricted token acquisition across all OAuth 2.0 grant flows.
Motivation and Context
Adobe IMS requires support for audience-restricted tokens to enhance security. The "resource" parameter allows clients to request tokens valid only for a specific target service, reducing token exposure if compromised. This implements RFC 8707 compliance as per IMS team requirements.
How Has This Been Tested?
Types of changes