Security Event Token (SET)

Created

  • 2020-07-01

Last Updated

  • 2026-05-11

Available Formats


Security Event Token Error Codes

Registration Procedure(s)

  • Specification Required

Expert(s)

  • Mike Jones, John Bradley

Reference

  • RFC 8935: Push-Based Security Event Token (SET) Delivery Using HTTP

Available Formats

Error Code Description Change Controller Reference
invalid_request The request body cannot be parsed as a SET or the Event Payload within the SET does not conform to the event's definition. IETF RFC 8935, Section 2.4
invalid_key One or more keys used to encrypt or sign the SET is invalid or otherwise unacceptable to the SET Recipient (expired, revoked, failed certificate validation, etc.). IETF RFC 8935, Section 2.4
invalid_issuer The SET Issuer is invalid for the SET Recipient. IETF RFC 8935, Section 2.4
invalid_audience The SET Audience does not correspond to the SET Recipient. IETF RFC 8935, Section 2.4
authentication_failed The SET Recipient could not authenticate the SET Transmitter. IETF RFC 8935, Section 2.4
access_denied The SET Transmitter is not authorized to transmit the SET to the SET Recipient. IETF RFC 8935, Section 2.4
invalid_state Indicates that a Verification event contained a "state" claim that does not match the value expected by the Receiver. OpenID - Shared Signals Working Group OpenID Shared Signals Framework Specification 1.0

Subject Identifier Formats

Registration Procedure(s)

  • Specification Required

Expert(s)

  • Prachi Jain

Reference

Available Formats

Format Name Format Description Change Controller Reference
account Subject Identifier based on "acct" URI IETF RFC 9493, Section 3
email Subject Identifier based on an email address IETF RFC 9493, Section 3
iss_sub Subject Identifier based on an issuer and subject IETF RFC 9493, Section 3
opaque Subject Identifier based on an opaque string IETF RFC 9493, Section 3
phone_number Subject Identifier based on a phone number IETF RFC 9493, Section 3
did Subject Identifier based on a decentralized identifier (DID) IETF RFC 9493, Section 3
uri Subject Identifier based on a Uniform Resource Identifier (URI) IETF RFC 9493, Section 3
aliases Subject Identifier that groups together multiple different Subject Identifiers for the same subject IETF RFC 9493, Section 3