Difference between revisions of "Security Event Token"
From MgmtWiki
(→Context) |
|||
| Line 5: | Line 5: | ||
Security Event Token (SET) RFC 8417 | Security Event Token (SET) RFC 8417 | ||
| − | |||
This specification defines the Security Event Token (SET) data | This specification defines the Security Event Token (SET) data | ||
| Line 16: | Line 15: | ||
Web Token (JWT), which can be optionally signed and/or encrypted. | Web Token (JWT), which can be optionally signed and/or encrypted. | ||
SETs can be distributed via protocols such as HTTP. | SETs can be distributed via protocols such as HTTP. | ||
| − | |||
==Problems== | ==Problems== | ||
Revision as of 15:02, 10 August 2018
Full Title or Meme
Security Event Token (SET) RFC 8417
Context
Security Event Token (SET) RFC 8417
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.
