Defer RFC 8693 token exchange for TEA 1.0 - #277
Merged
Merged
Conversation
Mark token exchange as outside the interoperable profile and remove the incomplete subject_token fields. Keeps the client_credentials baseline from CycloneDX#258, and narrows its token-exchange mention to an optional future extension pending a concrete consumer. Closes CycloneDX#273. Signed-off-by: Mehrn0ush <mehrnoush.vaseghi@gmail.com>
Collaborator
|
@taleodor what do you think? Ready to commit at your approval |
taleodor
approved these changes
Sep 14, 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
3 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.
Summary
subject_token/subject_token_typeso OpenAPI no longer looks like a supported exchange grantclient_credentials+ Bearer — the part of feat: token exchange endpoint and documentation #258 that Align /token with RFC 6749 Pragma and Basic credential encoding #271/Align /token responses with RFC 6749 cache and Basic encoding #272 tighten — while narrowing the token-exchange mention feat: token exchange endpoint and documentation #258 also introduced but never fully specifiedshall notassume exchange from TEA 1.0 conformance alone;client_credentialsremains required where auth is requiredCloses #273.