Patrick Cloke
|
fc03f7faa6
|
Remove query_auth from the specification per MSC2451.
|
2020-03-24 12:42:15 -04:00 |
|
Travis Ralston
|
82bed06d3f
|
The event *format* changes, not the version
|
2019-02-01 13:19:24 -07:00 |
|
Travis Ralston
|
33406e4662
|
Apply event format warnings to the remainder of the s2s spec
|
2019-02-01 10:08:30 -07:00 |
|
Konstantinos Sideris
|
192a6c2ab9
|
Use example.org on examples instead of domain.com which is a real domain
Signed-off-by: Konstantinos Sideris <sideris.konstantin@gmail.com>
|
2018-09-02 17:58:21 +03:00 |
|
Travis Ralston
|
25c77ab2d0
|
Define authorization requirements on federation swagger APIs
|
2018-08-09 08:37:35 -06:00 |
|
Travis Ralston
|
13a2b54bf9
|
query_auth consumes JSON
|
2018-08-03 13:57:43 -06:00 |
|
Travis Ralston
|
73958ecbff
|
Document /event_auth and /query_auth
/event_auth is a fairly easy endpoint to determine the use case of. /query_auth is a little harder to investigate and has a fairly interesting purpose: it appears to be used for the sending server to admit defeat and shop around for the right auth chain, correcting it's own perspective as it goes.
/query_auth is based off the following research points in synapse:
* 43ecfe0b10/synapse/handlers/federation.py (L1947-L1990)
* 43ecfe0b10/synapse/handlers/federation.py (L2049-L2187)
* 43ecfe0b10/synapse/handlers/federation.py (L1716-L1761)
* 43ecfe0b10/synapse/federation/federation_server.py (L393-L446)
* https://github.com/matrix-org/synapse/blob/master/synapse/federation/transport/server.py#L482-L487
|
2018-08-03 09:27:19 -06:00 |
|