Subject Identifiers for Security Event Tokens
RFC 9493
Revision differences
Document history
Date | By | Action |
---|---|---|
2024-04-29
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
2023-12-12
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
2023-12-06
|
(System) | IANA registries were updated to include RFC9493 |
2023-12-06
|
(System) | Received changes through RFC Editor sync (created alias RFC 9493, changed abstract to 'Security events communicated within Security Event Tokens may support a variety … Received changes through RFC Editor sync (created alias RFC 9493, changed abstract to 'Security events communicated within Security Event Tokens may support a variety of identifiers to identify subjects related to the event. This specification formalizes the notion of Subject Identifiers as structured information that describes a subject and named formats that define the syntax and semantics for encoding Subject Identifiers as JSON objects. It also establishes a registry for defining and allocating names for such formats as well as the JSON Web Token (JWT) "sub_id" Claim.', changed pages to 18, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2023-12-06, changed IESG state to RFC Published) |
2023-12-06
|
(System) | RFC published |