Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelogs/server_server/newsfragments/2360.breaking
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Require the `destination` field in server-to-server authentication. Contributed by @velikopter.
5 changes: 2 additions & 3 deletions content/server-server-api.md
Original file line number Diff line number Diff line change
Expand Up @@ -375,11 +375,10 @@ The authorization parameters to include are:
`origin` field from JSON described in step 1.
- `destination`: {{% added-in v="1.3" %}} the server name of the receiving
server. This is the same as the `destination` field from the JSON described
in step 1. For compatibility with older servers, recipients should accept
requests without this parameter, but MUST always send it. If this property
is included, but the value does not match the receiving server's name, the
in step 1. If the value does not match the receiving server's name, the
receiving server must deny the request with an HTTP status code 401
Unauthorized.
{{% changed-in v="1.19" %}} This field is now required.
- `key`: the ID, including the algorithm name, of the sending server's key used
to sign the request.
- `signature`: the signature of the JSON as calculated in step 1.
Expand Down
Loading