Author
Karl McGuinness
19 drafts reviewed, 23 reviews in total.
draft-ietf-oauth-identity-assertion-authz-grant
Identity Assertion JWT Authorization Grant (ID-JAG)
Two apps both use the same IdP for SSO. One wants to call the other's API on behalf of the user. Today that takes an interactive OAuth flow between the two apps, and the IdP never sees it.
draft-liu-mcguinness-oauth-bounded-work
Bounded Work Authorization, a Requirements Document for the Mission and Schemas Drafts
OAuth can revoke a token. It has no shared way to say "the task the user approved is over."
draft-mcguinness-oauth-cimd-sw-stmt
CIMD Software Statements, a Third-Party Review Pinned to the Exact Bytes of a Client's Metadata
A Client ID Metadata Document is self-asserted. The client publishes its own metadata at a URL and can change it at any time. An AS that allowlists the URL knows who the client is. It has…
draft-mcguinness-oauth-cimd-sw-stmt-lifecycle
CIMD Software Statement Lifecycle, Withdrawing and Replacing a Third-Party Review After the Grant Is Open
The CIMD Software Statement draft lets a third party sign off on one exact version of a client's Client ID Metadata Document. The AS checks that statement once, when the grant opens.…
draft-mcguinness-oauth-cimd-sw-stmt-registration
CIMD Software Statement Registration, Putting a Reviewed Client ID Metadata Document Through Dynamic Client Registration
The CIMD Software Statement draft lets a third party sign a digest of one exact version of a client's Client ID Metadata Document. That statement carries no metadata, only the digest.
draft-mcguinness-oauth-client-attesters
Client Attester Endorsement -01, an Alignment Update Update
This is a maintenance update. It catches up with ABCA -12 and SPIFFE Client Authentication -03. The mechanism is unchanged.
Client Attester Endorsement, the Missing Link Between ABCA and CIMD
This is one of two companion drafts published together on top of Attestation-Based Client Authentication (ABCA). The other is Client Instance Identification, reviewed in a separate post…
draft-mcguinness-oauth-client-instance-id
OAuth 2.0 Client Instance Identifiers -01, an Alignment Update Update
This is a maintenance update. It catches up with ABCA -12 and gets a shorter title. The mechanism is unchanged.
Client Instance Identification for Attestation-Based Client Authentication
This is the second of two companion drafts published together on top of Attestation-Based Client Authentication (ABCA). The first, Client Attester Endorsement, answers "who may attest for…
draft-mcguinness-oauth-client-ip-ranges
OAuth Client IP Range Metadata, Letting Clients Publish Their Egress IPs to the Authorization Server
Hosted OAuth clients usually call the token endpoint from a known set of IP addresses. Enterprises want to restrict access to those addresses. Today every vendor publishes its ranges in…
draft-mcguinness-oauth-grant-catalog
Grant Catalog, an Authenticated Feed That Tells the IdP What to Put in an ID-JAG
ID-JAG lets an enterprise IdP issue a grant that a SaaS application's authorization server redeems for an access token. The IdP has to know what that application will accept: the tenant…
draft-mcguinness-oauth-mission
Mission-Bound Authorization, a Task Record That Gates Every Token an Agent Gets
OAuth has grants and tokens. It has no object for "the task the user approved." An agent working on a multi-step job collects tokens for several audiences, refreshes them, and hands…
draft-mcguinness-oauth-mission-resource-access
Mission Resource Access, a Generic RAR Type for Resources, Actions, and Constraints
Mission-Bound Authorization records what a user approved for an agent's task as RAR authorizationdetails entries. It defines no entry type of its own. Every example in it uses…
draft-mcguinness-oauth-resource-token-resp
Resource Parameter in the Access Token Response, Telling the Client Which Resource a Token Is Good For
Resource Indicators lets a client say which resource it wants a token for. The AS never says what it actually did with that request. It can honor it, narrow it, swap it for a default, or…
draft-mcguinness-oauth-rfc9728bis
RFC 9728bis, Relaxing the Protected Resource Metadata Resource Match to a Path Prefix
Protected Resource Metadata has a strict rule. When a client follows a WWW-Authenticate challenge to a metadata document, the resource value in it must be identical to the URL the client…
draft-rosomakho-oauth-txn-challenge
Transaction Authorization Challenge Lets a Resource Server Demand Approval for One Specific Operation
An access token says the caller is allowed to talk to an API. It doesn't say a human approved this particular $5,000 payment.
draft-mcguinness-oauth-actor-profile
One Profile for the act Claim Across Grants, Access Tokens, and Transaction Tokens
RFC 8693 defined the act claim and then left most of the hard parts open. It says an actor is identified by sub, mentions that iss "might be necessary" to disambiguate, and calls the…
Making the act Claim Mean the Same Thing in Every Token
Alice tells an AI travel agent to book a trip. The agent gets a token from her enterprise IdP, trades it at the travel provider's AS for an access token, and calls a booking tool. The…
draft-mcguinness-oauth-actor-proofs
Actor Proofs, Having Each Actor Sign Its Own Delegation Hop
The Actor Profile puts actors in the act claim. The Actor Receipts companion has the AS sign a record of each hop. Both are the AS's word. A compromised or dishonest AS can mint a token…
draft-mcguinness-oauth-actor-receipts
Actor Receipts, Having Each Authorization Server Sign the Hop It Added
The Actor Profile puts the delegation chain in the act claim. The whole chain is covered by one signature, the current token issuer's. A resource server reading a three-hop chain is taking…
draft-mora-oauth-entity-profiles
Seven Strings to Say What Kind of Thing Is Calling
Nothing. The document history for -02 says "No changes" and a diff against -01 confirms it. This revision was posted on October 16, one day before -01 would have expired. It's a keepalive,…
draft-mcguinness-oauth-id-continuation-assertion
Identity Continuation Assertion for OAuth 2.0 Token Exchange
A workload receives an access token and needs to call the next service for the user, possibly after the user is gone. It holds nothing the next authorization server will accept. When…
Identity Continuation Assertion for OAuth 2.0 Token Exchange
The spec solves a narrow but real problem: how to continue a user's delegated identity across a chain of services when each service uses pairwise (audience-local) subject identifiers that…