]> Microsoft

mbj@microsoft.com http://self-issued.info/

Security RFC Request for Comments I-D Internet-Draft Assertion Simple Web Token Security Token SWT JavaScript Object Notation JSON JSON Web Token JWT JSON Web Signature JWS JSON Web Encryption JWE JSON Web Key JWK A JSON Web Key (JWK) is a JSON data structure that represents a set of public keys. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

A JSON Web Key (JWK) is a JSON data structure that represents a set of public keys as a JSON object . The JWK format is used to represent bare keys; representing certificate chains is an explicit non-goal of this specification. JSON Web Keys are referenced in JSON Web Signatures (JWSs) using the jku (JSON Key URL) header parameter.

A JSON data structure that represents a set of public keys. A JWK consists of a single JWK Container Object that contains an array of JWK Key Objects. A JSON object that contains an array of JWK Key Objects as a member. A JSON object that represents a single public key. For the purposes of this specification, this term always refers to the URL- and filename-safe Base64 encoding described in RFC 4648, Section 5, with the '=' padding characters omitted, as permitted by Section 3.2.

It is sometimes useful to be able to reference public key representations, for instance, in order to verify the signature on content signed with the corresponding private key. The JSON Web Key (JWK) data structure provides a convenient JSON representation for sets of public keys utilizing either the Elliptic Curve or RSA families of algorithms.

The following example JWK contains two public keys: one using an Elliptic Curve algorithm and a second one using an RSA algorithm. In both cases, integers are represented using the base64url encoding of their big endian representations.

A JWK consists of a JWK Container Object, which is a JSON object that contains an array of JWK Key Objects as a member. This section specifies the format of these objects.

A JWK Container Object is a JSON object containing a specific member. This member is: Member Name JSON Value Type Container Object Member Semantics keyvalues array The keyvalues member value contains an array of JWK Key Objects. This member is REQUIRED. Additional members MAY be present in the JWK Container Object. If present, they MUST be understood by implementations using that JWK.

A JWK Key Object is a JSON object containing specific members. Those members that are common to all key types are as follows: Member Name JSON Value Type Key Object Member Semantics algorithm string The algorithm member identifies the cryptographic algorithm family used with the key. Values defined by this specification are EC and RSA. Specific additional members are required to represent the key, depending upon the algorithm value. The algorithm value is case sensitive. This member is REQUIRED. use string The use member identifies the intended use of the key. Values defined by this specification are signature and encryption. Other values MAY be used. The use value is case sensitive. This member is OPTIONAL. keyid string The keyid (Key ID) member can be used to match a specific key. This can be used, for instance, to choose among a set of keys within the JWK during key rollover. The keyid value MAY correspond to a JWS kid value. The interpretation of the keyid value is unspecified. This member is OPTIONAL. Additional members MAY be present in the JWK Key Object. If present, they MUST be understood by implementations using that key.

JWKs can represent Elliptic Curve keys. In this case, the algorithm member value MUST be EC. Furthermore, these additional members MUST be present: Member Name JSON Value Type Key Object Member Semantics curve string The curve member identifies the cryptographic curve used with the key. Values defined by this specification are P-256, P-384 and P-521. Additional curve values MAY be used, provided they are understood by implementations using that Elliptic Curve key. The curve value is case sensitive. x string The x member contains the x coordinate for the elliptic curve point. It is represented as the base64url encoding of the coordinate's big endian representation. y string The y member contains the y coordinate for the elliptic curve point. It is represented as the base64url encoding of the coordinate's big endian representation.

JWKs can represent RSA keys. In this case, the algorithm member value MUST be RSA. Furthermore, these additional members MUST be present: Member Name JSON Value Type Key Object Member Semantics modulus string The modulus member contains the modulus value for the RSA public key. It is represented as the base64url encoding of the value's big endian representation. exponent string The exponent member contains the exponent value for the RSA public key. It is represented as the base64url encoding of the value's big endian representation.

JWKs make use of the base64url encoding as defined in RFC 4648. As allowed by Section 3.2 of the RFC, this specification mandates that base64url encoding when used with JWKs MUST NOT use padding. Notes on implementing base64url encoding can be found in the JWS specification.

No IANA actions are required by this specification.

TBD

&rfc2119; &RFC3447; &RFC4627; &RFC4648; National Institute of Standards and Technology Microsoft

mbj@microsoft.com http://self-issued.info/

Google

balfanz@google.com

independent

ve7jtb@ve7jtb.com

Microsoft

yarong@microsoft.com

Google

jpanzer@google.com

Nomura Research Institute

n-sakimura@nri.co.jp

Facebook

pt@fb.com

A JSON representation for RSA public keys was previously introduced in Magic Signatures.

-01 Changed algorithm member value for Elliptic Curve keys from ECDSA to EC, since Elliptic Curve keys can be used with more algorithms than just the Elliptic Curve Digital Signature Algorithm (ECDSA). Added OPTIONAL use member to identify intended key usage, especially since the same Elliptic Curve key should not be used for both signing and encryption operations. -00 Created first version based upon decisions made at the Internet Identity Workshop (IIW), as documented at http://self-issued.info/?p=390.