Yaron, Brian,
Responding to the request for prior-art alignment on actor delegation:
I implement a JOSE-based agent identity profile (AIC-JWT,
draft-wei-aic-jwt-00, companion to the X.509 AIC extension,
draft-wei-aic-identity-cert-00) whose delegation model maps onto the
three properties Brian stated. Concretely:
1. Signature chain with key fingerprints. A delegation is a
principal-signed grant (DelegationAuthorization) carried inside an
issuer-signed token, so the chain is two-layered and each layer's key
is bound by fingerprint: the principal key by SPKI hash (X.509
profile) or RFC 7638 JWK thumbprint (JWT profile), and the presenter
key by a cnf/jkt claim we require. The terminal relying party can
verify the whole chain offline; verification needs only the issuer
and principal trust anchors, with no pre-registration of the
presenter (agent) key.
2. Bounds that narrow hop by hop and fail closed. Each grant carries
an explicit capability set; an agent cannot receive capabilities the
principal did not grant, and unknown capability schemes are refused
rather than allowed. The effective authorization is the intersection
of the principal grant, the agent's declared capabilities, and the
relying party's policy.
3. Auditable reliance. The grant is evidence of a past decision; a
receipt or crossing record can bind it to one exact action and one
relying-party admission domain, so reliance is recorded separately
from the local allow/deny decision.
One structural difference worth stating: we keep the delegation grant
separate from the presentation token -- different lifetimes, trust
anchors, and revocation semantics -- so that authorization is not
collapsed into authentication.
Best,
Jijie Wei
_______________________________________________
OAuth mailing list -- [email protected]
To unsubscribe send an email to [email protected]
