A new version of the Security Event Token (SET) specification has been published containing measures that prevent any possibility of confusion between ID Tokens and SETs. Preventing confusion between SETs, access tokens, and other kinds of JWTs is also covered. Changes were:
- Added the Requirements for SET Profiles section.
- Expanded the Security Considerations section to describe how to prevent confusion of SETs with ID Tokens, access tokens, and other kinds of JWTs.
- Registered the
application/secevent+jwtmedia type and defined how to use it for explicit typing of SETs.
- Clarified the misleading statement that used to say that a SET conveys a single security event.
- Added a note explicitly acknowledging that some SET profiles may choose to convey event subject information in the event payload.
- Corrected an encoded claims set example.
- Applied grammar corrections.
This draft is intended to provide solutions to the issues that had been discussed in IETF 98 in Chicago and subsequently on the working group mailing list. Thanks for all the great discussions that informed this draft!
The specification is available at:
An HTML-formatted version is also available at: