{"id":1456,"date":"2015-09-13T23:24:23","date_gmt":"2015-09-14T06:24:23","guid":{"rendered":"https:\/\/self-issued.info\/?p=1456"},"modified":"2015-09-13T23:27:44","modified_gmt":"2015-09-14T06:27:44","slug":"jws-unencoded-payload-option-02","status":"publish","type":"post","link":"https:\/\/self-issued.info\/?p=1456","title":{"rendered":"JWS Unencoded Payload Option -02"},"content":{"rendered":"<p><span class=\"plain\"><img decoding=\"async\" align=\"right\" src=\"https:\/\/self-issued.info\/images\/ietf-logo.png\" alt=\"IETF logo\"\/><\/span>Draft -02 of the JWS Unencoded Payload Option specification makes these updates:<\/p>\n<ul>\n<li>Required that &#8220;<code>b64<\/code>&#8221; be integrity protected.<\/li>\n<li>Stated that if the JWS has multiple signatures and\/or MACs, the &#8220;<code>b64<\/code>&#8221; Header Parameter value MUST be the same for all of them.<\/li>\n<li>Stated that if applications use content encoding, they MUST specify whether the encoded or unencoded payload is used as the JWS Payload value.<\/li>\n<li>Reorganized the Unencoded Payload Content Restrictions section.<\/li>\n<li>Added an &#8220;updates&#8221; clause for RFC 7519 because this specification prohibits JWTs from using <code>\"b64\":false<\/code>.<\/li>\n<\/ul>\n<p>Thanks for the working group feedback that resulted in these improvements.<\/p>\n<p>The specification is available at:<\/p>\n<ul>\n<li><a href=\"http:\/\/tools.ietf.org\/html\/draft-ietf-jose-jws-signing-input-options-02\">http:\/\/tools.ietf.org\/html\/draft-ietf-jose-jws-signing-input-options-02<\/a><\/li>\n<\/ul>\n<p>An HTML formatted version is also available at:<\/p>\n<ul>\n<li><a href=\"https:\/\/self-issued.info\/docs\/draft-ietf-jose-jws-signing-input-options-02.html\">https:\/\/self-issued.info\/docs\/draft-ietf-jose-jws-signing-input-options-02.html<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Draft -02 of the JWS Unencoded Payload Option specification makes these updates: Required that &#8220;b64&#8221; be integrity protected. Stated that if the JWS has multiple signatures and\/or MACs, the &#8220;b64&#8221; Header Parameter value MUST be the same for all of them. Stated that if applications use content encoding, they MUST specify whether the encoded or [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[28,27,25],"tags":[],"class_list":["post-1456","post","type-post","status-publish","format-standard","hentry","category-cryptography","category-json","category-specifications"],"_links":{"self":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts\/1456","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=1456"}],"version-history":[{"count":3,"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts\/1456\/revisions"}],"predecessor-version":[{"id":1459,"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts\/1456\/revisions\/1459"}],"wp:attachment":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1456"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1456"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1456"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}