Security Event Token (SET)

Registries Included Below

Security Event Token Error Codes

Registration Procedure(s)

Specification Required

Expert(s)

Mike Jones, John Bradley

Reference

[RFC8935]

Available Formats

CSV

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	[RFC8935, 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	[RFC8935, Section 2.4]
invalid_issuer	The SET Issuer is invalid for the SET Recipient.	IETF	[RFC8935, Section 2.4]
invalid_audience	The SET Audience does not correspond to the SET Recipient.	IETF	[RFC8935, Section 2.4]
authentication_failed	The SET Recipient could not authenticate the SET Transmitter.	IETF	[RFC8935, Section 2.4]
access_denied	The SET Transmitter is not authorized to transmit the SET to the SET Recipient.	IETF	[RFC8935, Section 2.4]

Registration Procedure(s)

Specification Required

Expert(s)

Prachi Jain

Reference

[RFC9493][RFC Errata 7727]

Available Formats

CSV

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