Skip to content

Clarify subjects whose claims the ID-JAG conveys#98

Open
mcguinness wants to merge 1 commit into
mainfrom
clarify-claim-subjects
Open

Clarify subjects whose claims the ID-JAG conveys#98
mcguinness wants to merge 1 commit into
mainfrom
clarify-claim-subjects

Conversation

@mcguinness

Copy link
Copy Markdown
Collaborator

Summary

Clarifies which subjects' claims appear in an ID-JAG and how the IdP populates them, without changing normative behavior.

  • Names the three subjects: End-User (sub), OAuth client (client_id), and optional actor (act).
  • Anchors audience-scoped claim population to the same model IdPs already use for ID Tokens and SAML Assertions issued to the target Resource Authorization Server.
  • Preserves the prior text's OpenID Core reference and the "Identity Assertion plus authorization delegation" framing as the closing sentence.

Motivation

Implementer feedback indicated the previous text (The ID-JAG may contain additional authentication, identity, or authorization claims...) didn't make the implicit claim model obvious. In particular, audience-scoped authorization claims about the End-User (such as roles or entitlements at the target application) are first-class ID-JAG content. Naming the subjects explicitly and pointing to the existing IdP pattern resolves that without introducing new normative requirements or new claim shapes.

Test plan

  • Render with kramdown-rfc / xml2rfc and confirm cross-references resolve
  • Confirm no anchors changed

Rewrites the paragraph after the example JWT to name the three subjects
whose claims appear in an ID-JAG (End-User identified by `sub`, OAuth
client identified by `client_id`, and optional actor identified by `act`),
and to anchor audience-scoped claim population to the existing IdP
practice for ID Tokens and SAML Assertions issued to the same Resource
Authorization Server. Preserves the prior text's OpenID Core anchor and
"Identity Assertion plus authorization delegation" framing as the
closing sentence.
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.

1 participant