Author
Pieter Kasselman
5 drafts reviewed, 6 reviews in total.
draft-ietf-oauth-identity-chaining
Identity Chaining Is in the RFC Editor Queue
A client in one trust domain needs to call an API in another. Each domain has its own authorization server. The second domain needs to know which user the request is for and what was…
draft-ietf-oauth-spiffe-client-auth
OAuth SPIFFE Client Authentication
A workload running under SPIFFE already has an attested credential, its SVID. To call an OAuth token endpoint today it still needs a second credential, a client secret or a privatekeyjwt…
draft-ietf-wimse-aims
AI Identity Management System (AIMS)
People keep inventing new authentication and authorization schemes for AI agents. Most of them rebuild things that already exist.
draft-fletcher-oauth-txn-token-chaining-profile
Transaction Token Chaining Profile Adds Transaction Context Update
This is a small update. Revision -01 was published October 26, six weeks after -00. Three things changed, and each one traces to a GitHub issue rather than to list feedback.
Taking a Transaction Token Across the Trust Boundary
Transaction Tokens carry the authorization context of a request through a company's internal call chain. They are deliberately scoped to one trust domain. The Txn-Token spec says a…
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.