wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

No custom HTTP headers

Browse source 
Use the obvious way: in the same place as the ID server address
This commit is contained in:
David Baker 2019-06-26 17:56:41 +01:00
parent 2694bb1090
commit 21b9eaf8de
1 changed files with 7 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

10
proposals/2140-terms-of-service-2.md
View file

@ -77,9 +77,13 @@ API, as specified in [MSC1961](https://github.com/matrix-org/matrix-doc/issues/1
When clients supply an identity server to the Homeserver in order for the Homeserver When clients supply an identity server to the Homeserver in order for the Homeserver
to make calls to the IS on its behalf, it must also supply its access token for the to make calls to the IS on its behalf, it must also supply its access token for the
Identity Server either as the `is_token` query parameter or a bearer token in the Identity Server alongside in the `is_token` key of the same JSON object. That is,
`X-Identity-Authorization` HTTP header with the same syntax as an `Authorizationn` in the main request object for a `requestToken` request and in the `threepidCreds`
header. object when supplying 3PID credentials (eg. in the `m.email.identity` UI auth stage).
Exxceptions to this are any requests where the only IS operation the Homeserver may
perform is unbinding, ie. `/_matrix/client/r0/account/deactivate` and
`/_matrix/client/r0/account/3pid/delete`, in which case the unbind is authenticated
by a signed request from the Homeserver.
### IS Register API ### IS Register API