8000 Identity Assertion JWT Authorization Grant · Issue #43971 · keycloak/keycloak · GitHub
[go: up one dir, main page]

Skip to content

Identity Assertion JWT Authorization Grant #43971

Open
0 of 2 issues completed
Open

Description

@stianst

Description

Identity Assertion JWT Authorization Grant builds on Identity Chaining Across Trust Domains to cover scenarios within a single enterprise.

An example use-case enabled by ID-JAG is a scenario where an enterprise uses a SaaS service configured with the corporate IdP for single sign-on using, and at the same time allowing direct API access to a resource server by allowing an ID-JAG to be used to obtain an access token from the SaaS service authorization server.

Value Proposition

Enables SaaS services to offer better integration with the enterprise IdP. ID-JAG will also be included in the next MCP specification.

Goals

  • Add support for ID-JAG to Keycloak

Non-Goals

Discussion

No response

Notes

No response

Activity

  1. added theissue type on Nov 5, 2025
  2. tnorimat commented on Nov 5, 2025

    @tnorimat
    Contributor

    @stianst Thank you for creating the issue. I would like to write its details afterwards.

  3. tnorimat commented on Nov 5, 2025

    @tnorimat
    Contributor

    Identity Assertion JWT Authorization Grant leverages RFC 8693 Token Exchange and RFC 7523 JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants and is discussed in the MCP community SEP-646: Enterprise-Managed Authorization Profile for MCP. The spec is for enterprise-ready MCP.

  4. tnorimat commented on Jan 30, 2026

    @tnorimat
    Contributor

    @stianst Hello, my colleague is now working for the issue. The PR will be submitted afterwards.

  5. added this to the 26.7.0 milestone on Apr 29, 2026
  6. tnorimat commented on May 17, 2026

    @tnorimat
    Contributor

    @stianst Hello,

    Regarding ID-JAG, there are two roles: consumer and issuer.
    The existing issues/PRs are about keycloak as a consumer of ID-JAG.
    Therefore, how about adding the goal to the issue as follows?

    • Keycloak works as a consumer of ID-JAG

    Regarding ID -JAG as an issuer, my colleague created the issue for ID-JAG as an issuer .

  7. modified the milestones: 26.7.0, 26.8.0 on Jun 15, 2026
  8. added
    area/token-exchange/federatedFederated token exchange — JWT Authorization Grant (RFC 7523), IdP trust
    status/labeled-by-botIssue type or area was assigned automatically by the triage bot
    on Nov 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Fields

Value

None yet

Effort

None yet

Votes

16

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions

0