{"id":502,"date":"2011-04-30T23:55:44","date_gmt":"2011-05-01T06:55:44","guid":{"rendered":"https:\/\/self-issued.info\/?p=502"},"modified":"2012-09-18T16:01:09","modified_gmt":"2012-09-18T23:01:09","slug":"json-web-key-jwk-specification","status":"publish","type":"post","link":"https:\/\/self-issued.info\/?p=502","title":{"rendered":"JSON Web Key (JWK) Specification"},"content":{"rendered":"

I’ve posted the JSON Web Key (JWK) specification<\/a> for representing public keys as JSON objects based on the decisions made at the last IIW<\/a>. The introduction to the spec reads:<\/p>\n

\nA 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.\n<\/p><\/blockquote>\n

An example from the spec is:<\/p>\n

{\"keyvalues\":
\n  [
\n    {\"algorithm\":\"ECDSA\",
\n     \"curve\":\"P-256\",
\n     \"x\":\"MKBCTNIcKUSDii11ySs3526iDZ8AiTo7Tu6KPAqv7D4\",
\n     \"y\":\"4Etl6SRW2YiLUrN5vfvVHuhp7x8PxltmWWlbbM4IFyM\",
\n     \"keyid\":\"1\"},<\/p>\n

    {\"algorithm\":\"RSA\",
\n     \"modulus\": \"0vx7agoebGcQSuuPiLJXZptN9nndrQmbXEps2aiAFbWhM78LhWx4cbbfAAtVT86zwu1RK7aPFFxuhDR1L6tSoc_BJECPebWKRXjBZCiFV4n3oknjhMstn64tZ_2W-5JsGY4Hc5n9yBXArwl93lqt7_RN5w6Cf0h4QyQ5v-65YGjQR0_FDW2QvzqY368QQMicAtaSqzs8KJZgnYb9c7d0zgdAZHzu6qMQvRL5hajrn1n91CbOpbISD08qNLyrdkt-bFTWhAI4vMQFh6WeZu0fM4lFd2NcRwr3XPksINHaQ-G_xBniIqbw0Ls1jF44-csFCur-kEgU8awapJzKnqDKgw\",
\n     \"exponent\":\"AQAB\",
\n     \"keyid\":\"2011-04-29\"}
\n  ]
\n}<\/code><\/p>\n

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