{"id":2152,"date":"2021-03-19T13:38:09","date_gmt":"2021-03-19T20:38:09","guid":{"rendered":"https:\/\/self-issued.info\/?p=2152"},"modified":"2021-03-19T13:38:09","modified_gmt":"2021-03-19T20:38:09","slug":"oauth-2-0-jwt-secured-authorization-request-jar-updates-addressing-remaining-review-comments","status":"publish","type":"post","link":"https:\/\/self-issued.info\/?p=2152","title":{"rendered":"OAuth 2.0 JWT Secured Authorization Request (JAR) updates addressing remaining review comments"},"content":{"rendered":"

\"OAuth<\/span>After the OAuth 2.0 JWT Secured Authorization Request (JAR)<\/b> specification was sent to the RFC Editor<\/a>, the IESG requested an additional round of IETF feedback. We’ve published an updated draft addressing the remaining review comments, specifically, SecDir comments from Watson Ladd. The only normative change made since the 28 was to change the MIME Type from “oauth.authz.req+jwt<\/code>” to “oauth-authz-req+jwt<\/code>“, per advice from the designated experts.<\/p>\n

As a reminder, this specification takes the JWT Request Object from Section 6 of OpenID Connect Core<\/b> (Passing Request Parameters as JWTs<\/i>)<\/a> and makes this functionality available for pure OAuth 2.0 applications — and does so without introducing breaking changes. This is one of a series of specifications bringing functionality originally developed for OpenID Connect to the OAuth 2.0 ecosystem. Other such specifications included OAuth 2.0 Dynamic Client Registration Protocol<\/b> [RFC 7591<\/a>] and OAuth 2.0 Authorization Server Metadata<\/b> [RFC 8414<\/a>].<\/p>\n

The specification is available at:<\/p>\n