feat(auth): add EMA refresh-token conformance scenario - #484
Open
nicksteele-oai wants to merge 1 commit into
Open
feat(auth): add EMA refresh-token conformance scenario#484nicksteele-oai wants to merge 1 commit into
nicksteele-oai wants to merge 1 commit into
Conversation
nicksteele-oai
marked this pull request as ready for review
September 2, 2026 21:55
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
1 participant
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.
The existing EMA client scenario only exercises an ID-token subject. Add
auth/enterprise-managed-authorization-refresh-tokenfor clients supporting the optional refresh-token exchange described in ID-JAG §4.3.Reuse the existing scenario and TypeScript example while retaining the ID-token profile. The new fixture checks IdP client binding, audience/resource restrictions, scope narrowing, and completed MCP access with the issued token. Eleven negative cases cover invalid exchanges, scope escalation, and incomplete or invalid MCP access. README is unchanged.
Validation:
npm run check,npm run build, andnpm test: 536 tests passed.dc26f27a8228: 11 checks passed, including both exchanges andtools/list/tools/call.SDK runs used local fixtures with MCP
2025-11-25and--force; live IdP interoperability remains untested.Related: #470 covers Resource AS conformance; this draft adds client-side coverage.