try & clarify that HS signature isn't the only acceptable auth for unbind

This commit is contained in:
David Baker 2019-07-04 18:38:31 +01:00
parent 1a669348d8
commit 30dcc28f9b

View file

@ -91,15 +91,16 @@ possible.
OpenID authentication in the IS API will work the same as in the Integration Manager OpenID authentication in the IS API will work the same as in the Integration Manager
API, as specified in [MSC1961](https://github.com/matrix-org/matrix-doc/issues/1961). API, as specified in [MSC1961](https://github.com/matrix-org/matrix-doc/issues/1961).
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
to make calls to the IS on its behalf, it must also supply its access token for the Homeserver to make calls to the IS on its behalf, it must also supply its
Identity Server alongside in the `is_token` key of the same JSON object. That is, access token for the Identity Server alongside in the `is_token` key of the
in the main request object for a `requestToken` request and in the `threepidCreds` same JSON object. That is, in the main request object for a `requestToken`
object when supplying 3PID credentials (eg. in the `m.email.identity` UI auth stage). request and in the `threepidCreds` object when supplying 3PID credentials (eg.
Exceptions to this are any requests where the only IS operation the Homeserver may in the `m.email.identity` UI auth stage). Exceptions to this are any requests
perform is unbinding, ie. `/_matrix/client/r0/account/deactivate` and where the only IS operation the Homeserver may perform is unbinding, ie.
`/_matrix/client/r0/account/3pid/delete`, in which case the unbind is authenticated `/_matrix/client/r0/account/deactivate` and
by a signed request from the Homeserver. `/_matrix/client/r0/account/3pid/delete`, in which case the unbind will be
authenticated by a signed request from the Homeserver.
### HS Register API ### HS Register API