Compare commits

...

4 commits

Author SHA1 Message Date
Logan Devine 1d3b4dff09
Merge 57c6273162 into fe5a195f4a 2026-03-05 11:11:13 -08:00
Logan Devine 57c6273162
Update 2329.clarification 2026-03-04 08:24:32 -08:00
Logan Devine f49e6858f7
Add newsfragment 2026-03-04 08:22:29 -08:00
Logan Devine ba3674da8e
add link to JSON signing algorithm on federation auth section 2026-03-04 08:13:13 -08:00
2 changed files with 7 additions and 6 deletions

View file

@ -0,0 +1 @@
Add link to JSON signing algorithm in server-server auth section for clarity. Contributed by @thetayloredman.

View file

@ -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: