JWT - Revision history

Tom: /* Solutions */

2023-07-25T04:51:52Z

‎Solutions

Tom: /* Solutions */

2023-07-25T04:49:17Z

‎Solutions

Tom: /* Solutions */

2023-07-25T04:43:02Z

‎Solutions

Tom: /* Context */

2020-01-17T00:11:33Z

‎Context

Tom: /* Context */

2020-01-17T00:10:45Z

‎Context

Tom: /* Other reference material */

2020-01-17T00:04:04Z

‎Other reference material

Tom: /* Other reference material */

2020-01-17T00:02:06Z

‎Other reference material

Tom: /* Other reference material */

2020-01-16T05:57:08Z

‎Other reference material

Tom: /* Other reference material */

2020-01-16T05:37:30Z

‎Other reference material

Tom: /* Other reference material */

2020-01-16T05:37:11Z

‎Other reference material

@@ Line 12: / Line 12: @@
 ==Solutions==
 *The RFC 7519 definition of the [https://tools.ietf.org/html/rfc7519 JSON Web Token (JWT)]. The abstract from the spec <blockquote>   JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties.  The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature ([[JWS]]) structure or as the plaintext of a JSON Web Encryption ([[JWE]]) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.</blockquote>
 *Justin Richer has some suggestions.<ref>Justin Richer, ''Moving On from OAuth 2: A Proposal.'' https://medium.com/@justinsecurity/moving-on-from-oauth-2-629a00133ade</ref>
-[[File:JTW Jason Token.jpg|thumb|right|400px]]
 ==References==

@@ Line 13: / Line 13: @@
 *The RFC 7519 definition of the [https://tools.ietf.org/html/rfc7519 JSON Web Token (JWT)]. The abstract from the spec <blockquote>   JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties.  The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature ([[JWS]]) structure or as the plaintext of a JSON Web Encryption ([[JWE]]) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.</blockquote>
 *Justin Richer has some suggestions.<ref>Justin Richer, ''Moving On from OAuth 2: A Proposal.'' https://medium.com/@justinsecurity/moving-on-from-oauth-2-629a00133ade</ref>
-[[File:JTW Jason Token.jpg]]
+[[File:JTW Jason Token.jpg|thumb|right|400px]]
 ==References==

@@ Line 13: / Line 13: @@
 *The RFC 7519 definition of the [https://tools.ietf.org/html/rfc7519 JSON Web Token (JWT)]. The abstract from the spec <blockquote>   JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties.  The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature ([[JWS]]) structure or as the plaintext of a JSON Web Encryption ([[JWE]]) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.</blockquote>
 *Justin Richer has some suggestions.<ref>Justin Richer, ''Moving On from OAuth 2: A Proposal.'' https://medium.com/@justinsecurity/moving-on-from-oauth-2-629a00133ade</ref>
 ==References==

@@ Line 4: / Line 4: @@
 ==Context==
 *In [[OAuth 2.0]] and other specs from the Open ID Foundation, there was a need for a small packed of identity information that could be coded and include in an HTTP header.
-*Since that humble beginning the JWT format has been extended and move to typically be delivered in the body of a post message which gets around the size limit experienced in an HTTP header.
+*Since that humble beginning the JWT format has been extended in scope and more typically is delivered in the body of a post message which gets around the size limit experienced in an HTTP header.
 ==Problems==

@@ Line 3: / Line 3: @@
 ==Context==
-In [[OAuth 2.0]] and other specs from the Open ID Foundation, there was a need for a small packed of identity information that could be coded and include in a HTTP header.
+*In [[OAuth 2.0]] and other specs from the Open ID Foundation, there was a need for a small packed of identity information that could be coded and include in an HTTP header.
 ==Problems==

@@ Line 18: / Line 18: @@
 # [https://blog.angular-university.io/angular-jwt/ JWT: The Complete Guide to JSON Web Tokens] from the folks that brought you angular.
 # [https://jwt.io/ JWT.IO]] allows you to decode, verify and generate JWT.
-# RFC 7518 JSON Web Algorithms (JWA)<blockquote>This specification registers cryptographic algorithms and identifiers to be used with the JSON Web Signature (JWS), JSON Web Encryption (JWE), and JSON Web Key (JWK) specifications.  It defines several IANA registries for these identifiers.</blockquote>
+# RFC 7515 JSON Web Signature (JWS) <blockquote>represents content secured with digital signatures or Message Authentication Codes (MACs) using JSON-based data structures.  Cryptographic algorithms and identifiers for use with this specification are described in the separate JSON Web  Algorithms (JWA) specification and an IANA registry defined by that  specification.  Related encryption capabilities are described in the separate JSON Web Encryption (JWE) specification.</blockquote>
 # RFC 7516 Json Web Encryption ([[JWE]])<blockquote>represents encrypted content using JSON-based data structures.  Cryptographic algorithms and identifiers for use with this specification are described in the separate JSON Web Algorithms (JWA) specification and IANA registries defined by that specification.  Related digital signature and Message Authentication Code (MAC) capabilities are described in the separate JSON Web Signature (JWS) specification</blockquote>
 # RFC 6749 The OAuth 2.0 Authorization Framework specification
 # RFC 8252 OAuth 2.0 for Native Apps Specification
 [[Category:Glossary]]
 [[Category:Standard]]