From 0a6886e73c63f64286d16d98e9ee0384b06239c2 Mon Sep 17 00:00:00 2001 From: Richard van der Hoff Date: Wed, 22 Mar 2017 07:39:06 +0000 Subject: [PATCH] Fix broken link in spec --- specification/appendices/signing_json.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/appendices/signing_json.rst b/specification/appendices/signing_json.rst index bc76c89a..30bf91a0 100644 --- a/specification/appendices/signing_json.rst +++ b/specification/appendices/signing_json.rst @@ -91,7 +91,7 @@ Signing Details JSON is signed by encoding the JSON object without ``signatures`` or keys grouped as ``unsigned``, using the canonical encoding described above. The JSON bytes are then signed using the -signature algorithm and the signature is encoded using `unpadded Base64`._ +signature algorithm and the signature is encoded using `unpadded Base64`_. The resulting base64 signature is added to an object under the *signing key identifier* which is added to the ``signatures`` object under the name of the entity signing it which is added back to the original JSON object