Security Event Token (SET)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 28
- Abstract
- 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.
- Publication Date
- 2018-07-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC8417- Link
- https://doi.org/10.17487/RFC8417
- Author(s)
- Phil HuntMichael B. JonesWilliam DennissMorteza Ansari
- Keyword(s)
- Media Identity, Security, JSON, JWT
Latest version of IETF RFC 8417
Document Versions — IETF RFC 8417
-
▶ IETF RFC 8417 (2018-07-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IANA, "Media Types", < http://www.iana.org/assignments/media-types >. EXTERNAL
- IANA, "JSON Web Token Claims", < http://www.iana.org/assignments/jwt >. EXTERNAL
- IANA, "Structured Syntax Suffix", < https://www.iana.org/assignments/ media-type-structured-suffix/ >. EXTERNAL
- IETF RFC 2119 [Active*]
- IETF RFC 3629 [Active*]
- IETF RFC 3986 [Active, Amended*]
- IETF RFC 5246 [Superseded*]
- IETF RFC 6125 [Superseded*]
- IETF RFC 6749 [Active*]
- IETF RFC 7515 [Active*]
- IETF RFC 7516 [Active*]
- IETF RFC 7519 [Active*]
- IETF RFC 7525 [Superseded*]
- IETF RFC 8174 [Active*]
Bibliographic Reference(s)
- IETF.draft-ietf-oauth-jwt-bcp-03 — JWT-BCP EXTERNAL
- Scurtescu, M., Backman, A., Hunt, P., and J. Bradley, "OpenID RISC Event Types 1.0", April 2018, < http://openid.net/specs/ openid-risc-event-types-1_0.html >. EXTERNAL
- Jones, M. and J. Bradley, "OpenID Connect Back-Channel Logout 1.0", January 2017, < http://openid.net/specs/ openid-connect-backchannel-1_0.html >. EXTERNAL
- Sakimura, N., Bradley, J., Jones, M., de Medeiros, B., and C. Mortimore, "OpenID Connect Core 1.0", November 2014, < http://openid.net/specs/openid-connect-core-1_0.html >. EXTERNAL
- IETF RFC 2046 [Active, Amended*]
- IETF RFC 6838 [Active*]
- IETF RFC 7644 [Active*]
- IETF RFC 8055 [Active*]
- IETF RFC 8225 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC8417.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 8417, Security Event Token (SET). Available at https://doi.org/10.17487/RFC8417
Snippet:
IETF RFC 8417, Security Event Token (SET). Available at https://doi.org/10.17487/RFC8417
HTML (ISO 690 compliant)
Preview:
IETF RFC 8417, Security Event Token (SET). Available at https://doi.org/10.17487/RFC8417
Snippet:
<span class="citation"><cite>IETF RFC 8417</cite>, Security Event Token (SET). Available at <a href="https://doi.org/10.17487/RFC8417" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8417</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc8417">IETF RFC 8417</cite>, Security Event Token (SET) <span class="doi">10.17487/RFC8417</span> </li>
Referenced By
- IETF RFC 8725 [Active*]