|
|
@ -1145,6 +1145,12 @@ client supports it, the client should redirect the user to the
|
|
|
|
is complete, the client will need to submit a `/login` request matching
|
|
|
|
is complete, the client will need to submit a `/login` request matching
|
|
|
|
`m.login.token`.
|
|
|
|
`m.login.token`.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
{{% http-api spec="client-server" api="login" %}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
{{% http-api spec="client-server" api="refresh" %}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
{{% http-api spec="client-server" api="logout" %}}
|
|
|
|
|
|
|
|
|
|
|
|
#### Appservice Login
|
|
|
|
#### Appservice Login
|
|
|
|
|
|
|
|
|
|
|
|
{{% added-in v="1.2" %}}
|
|
|
|
{{% added-in v="1.2" %}}
|
|
|
@ -1182,12 +1188,6 @@ If the access token does correspond to an appservice, but the user id does
|
|
|
|
not lie within its namespace then the homeserver will respond with an
|
|
|
|
not lie within its namespace then the homeserver will respond with an
|
|
|
|
errcode of `M_EXCLUSIVE`.
|
|
|
|
errcode of `M_EXCLUSIVE`.
|
|
|
|
|
|
|
|
|
|
|
|
{{% http-api spec="client-server" api="login" %}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
{{% http-api spec="client-server" api="refresh" %}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
{{% http-api spec="client-server" api="logout" %}}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#### Login Fallback
|
|
|
|
#### Login Fallback
|
|
|
|
|
|
|
|
|
|
|
|
If a client does not recognize any or all login flows it can use the
|
|
|
|
If a client does not recognize any or all login flows it can use the
|
|
|
@ -2646,4 +2646,4 @@ systems.
|
|
|
|
{{< cs-module name="spaces" >}}
|
|
|
|
{{< cs-module name="spaces" >}}
|
|
|
|
{{< cs-module name="event_replacements" >}}
|
|
|
|
{{< cs-module name="event_replacements" >}}
|
|
|
|
{{< cs-module name="threading" >}}
|
|
|
|
{{< cs-module name="threading" >}}
|
|
|
|
{{< cs-module name="reference_relations" >}}
|
|
|
|
{{< cs-module name="reference_relations" >}}
|
|
|
|