{"id":1891,"date":"2018-07-10T08:04:46","date_gmt":"2018-07-10T15:04:46","guid":{"rendered":"https:\/\/self-issued.info\/?p=1891"},"modified":"2018-07-10T08:04:46","modified_gmt":"2018-07-10T15:04:46","slug":"security-event-token-set-is-now-rfc-8417","status":"publish","type":"post","link":"https:\/\/self-issued.info\/?p=1891","title":{"rendered":"Security Event Token (SET) is now RFC 8417"},"content":{"rendered":"<p><span class=\"plain\"><img decoding=\"async\" align=\"right\" src=\"https:\/\/self-issued.info\/images\/ietf-logo.png\" alt=\"IETF logo\"\/><\/span>The Security Event Token (SET) specification is now <a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc8417.txt\">RFC 8417<\/a>.  The abstract describes the specification as:<\/p>\n<blockquote><p>\nThis 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.\n<\/p><\/blockquote>\n<p>SETs are already in use to represent <a href=\"http:\/\/openid.net\/specs\/openid-connect-backchannel-1_0.html\">OpenID Connect Back-Channel Logout<\/a> tokens and to represent <a href=\"http:\/\/openid.net\/wg\/risc\/\">Risk and Incident Sharing and Coordination (RISC)<\/a> events.  Thanks to my co-editors, members of the IETF ID Events mailing list, and members of the IETF Security Events working group for making this standard a reality!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Security Event Token (SET) specification is now RFC 8417. The abstract describes the specification as: 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 [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,32,27,14,25],"tags":[],"class_list":["post-1891","post","type-post","status-publish","format-standard","hentry","category-claims","category-ietf","category-json","category-openid","category-specifications"],"_links":{"self":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts\/1891","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1891"}],"version-history":[{"count":2,"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts\/1891\/revisions"}],"predecessor-version":[{"id":1894,"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts\/1891\/revisions\/1894"}],"wp:attachment":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1891"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1891"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1891"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}