Skip to content

Add WIF extension based on WAG as experimental - #42

Open
pcarleton wants to merge 14 commits into
mainfrom
paulc/sep3392-wif-wag-minimal
Open

pcarleton wants to merge 14 commits into
mainfrom
paulc/sep3392-wif-wag-minimal

Conversation

@pcarleton

Copy link
Copy Markdown
Member

No description provided.

PieterKas and others added 12 commits December 5, 2025 17:31
Clarified the prerequisites for the authorization server and improved the description of the message flow. Updated terminology for issuer trust and added details on token validation.
Move Pieter Kasselman's Workload Identity Federation text from
specification/draft/ to
specification/experimental/workload-identity-federation.mdx and list it in
README.md. The only changes to the text are the ones Prettier makes, so the
format check passes.
Replace the introduction, requirements and standards list with one paragraph that cites the Workload Authorization Grant draft, and map the MCP roles to the roles it defines.
Point to the draft for the typ header and claims instead of listing them. The audience becomes the authorization server's issuer identifier, and the subject an opaque identifier. Keep two MCP rules: resource is required and the grant type is advertised in metadata. Update the example to match.
Drop the flow diagram and steps, issuer key discovery, trust configuration, trust relationships, multi-tenancy, and the response and error examples.
Replace the restated considerations with references to the draft and to MCP Authorization.
Say that workload identity federation is an established pattern, that MCP
adopts it and bases it on WAG, and that this does not preclude other
mechanisms. Remove the TODO on a second assertion profile, which this
replaces. List the authors.
@pcarleton
pcarleton marked this pull request as ready for review November 9, 2026 16:56
@pcarleton

Copy link
Copy Markdown
Member Author

cc @PieterKas for initial review

pcarleton and others added 2 commits November 10, 2026 14:38
Co-authored-by: PieterKas <90690777+PieterKas@users.noreply.github.com>
Co-authored-by: PieterKas <90690777+PieterKas@users.noreply.github.com>
@figitaki

Copy link
Copy Markdown

Implementer feedback against this PR and WAG -02:

  1. Please advertise urn:ietf:params:oauth:grant-profile:wag through authorization_grant_profiles_supported, as WAG §8 describes, in addition to advertising the RFC 7523 JWT-bearer grant type. The latter alone does not distinguish WAG from other assertion profiles.
  2. The Security Considerations reference says WAG section 9; it is section 10 in -02. An anchor link would avoid the next renumbering.
  3. It would help to state the boundary when composing this extension with Mark DPoP as experimental extension #38: a DPoP-bound access token does not by itself make the WAG sender-constrained at redemption. A copied bearer WAG can otherwise be redeemed with a different DPoP key. Optional grant binding needs explicit AS support discovery and a WIP-registration policy, since this extension has no per-Agent client registration.

The grant-binding design discussion belongs in WAG issue #20; I am not proposing that MCP independently define that profile here. The first two points are independent interoperability/editorial fixes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants