From ba3674da8ed7941b8dc4f7b1171e3bb154a9c55e Mon Sep 17 00:00:00 2001 From: Logan Devine Date: Wed, 4 Mar 2026 08:13:13 -0800 Subject: [PATCH] add link to JSON signing algorithm on federation auth section --- content/server-server-api.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/content/server-server-api.md b/content/server-server-api.md index bc393ae9..50104ed5 100644 --- a/content/server-server-api.md +++ b/content/server-server-api.md @@ -277,12 +277,12 @@ queried from multiple servers to mitigate against DNS spoofing. Every HTTP request made by a homeserver is authenticated using public key digital signatures. The request method, target and body are signed -by wrapping them in a JSON object and signing it using the JSON signing -algorithm. The resulting signatures are added as an Authorization header -with an auth scheme of `X-Matrix`. Note that the target field should -include the full path starting with `/_matrix/...`, including the `?` -and any query parameters if present, but should not include the leading -`https:`, nor the destination server's hostname. +by wrapping them in a JSON object and signing it using the [JSON signing +algorithm](/appendices#signing-json). The resulting signatures are added +as an Authorization header with an auth scheme of `X-Matrix`. Note that +the target field should include the full path starting with `/_matrix/...`, +including the `?` and any query parameters if present, but should not +include the leading `https:`, nor the destination server's hostname. Step 1 sign JSON: