RFC 8417: Security Event Token (SET)
In plain English — editorial summary, not part of the RFC
This specification defines the Security Event Token (SET) data structure. A SET describes statements of fact from the perspective of an issuer about a subject. These statements of fact represent an event that occurred directly to or about a security subject, for example, a statement about the issuance or revocation of a token on behalf of a subject. This specification is intended to enable representing security- and identity-related events. A SET is a JSON Web Token (JWT), which can be optionally signed and/or encrypted. SETs can be distributed via protocols such as HTTP.
Document record
- Document ID
- RFC8417
- Published
- July 2018
- Authors
- P. Hunt; M. Jones; W. Denniss; M. Ansari
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 28
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8725JSON Web Token Best Current PracticesCurrent
February 2020
- RFC 8414OAuth 2.0 Authorization Server MetadataCurrent
June 2018
- RFC 8392CBOR Web Token (CWT)Current
May 2018
- RFC 8693OAuth 2.0 Token ExchangeCurrent
January 2020
- RFC 8935Push-Based Security Event Token (SET) Delivery Using HTTPCurrent
November 2020
- RFC 8936Poll-Based Security Event Token (SET) Delivery Using HTTPCurrent
November 2020
- RFC 9101The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR)Current
August 2021
- RFC 7519JSON Web Token (JWT)Updated
May 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?