Repository navigation
feat(auth): support OIDC ID-token subjects in enterprise exchange - #1385
Merged
Merged
Conversation
github-actions
Bot
added
T-test
Contributor
|
@DaleSeo (assignment failed) is on triage rotation this week and is the reviewer for this one. Labels come from the PR labeler. Please review the change. Automated triage. Labels are a first pass and the assigned maintainer has the final say. |
jif-oai
force-pushed
the
jif/ema-id-token
branch
from
October 22, 2026 10:40
2eb187f to
b146a3d
Compare
jif-oai
changed the title
DaleSeo
reviewed
Oct 22, 2026
Merged
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.
Allow EMA callers to exchange an OIDC ID token for an ID-JAG using
EmaExchangeRequest::new_with_id_token. The existing constructor keeps the refresh-token subject, and both paths use the same validation, client authentication, and resource-bound redemption. ID-token freshness and renewal remain with the caller.