|
|
@ -234,7 +234,7 @@ Token-based
|
|
|
|
:Type:
|
|
|
|
:Type:
|
|
|
|
``m.login.token``
|
|
|
|
``m.login.token``
|
|
|
|
:Description:
|
|
|
|
:Description:
|
|
|
|
The client submits a username and token that was generated by the server.
|
|
|
|
The client submits a username and token.
|
|
|
|
|
|
|
|
|
|
|
|
To respond to this type, reply with an auth dict as follows::
|
|
|
|
To respond to this type, reply with an auth dict as follows::
|
|
|
|
|
|
|
|
|
|
|
@ -248,9 +248,8 @@ To respond to this type, reply with an auth dict as follows::
|
|
|
|
The ``nonce`` should be a random string generated by the client for the
|
|
|
|
The ``nonce`` should be a random string generated by the client for the
|
|
|
|
request. The same ``nonce`` should be used if retrying the request.
|
|
|
|
request. The same ``nonce`` should be used if retrying the request.
|
|
|
|
|
|
|
|
|
|
|
|
The ``token`` may be discovered from e.g. an email or dynamically generated QR
|
|
|
|
There are many ways a client may receive a ``token``, including via an email or
|
|
|
|
code.
|
|
|
|
from an existing logged in device.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
OAuth2-based
|
|
|
|
OAuth2-based
|
|
|
|
~~~~~~~~~~~~
|
|
|
|
~~~~~~~~~~~~
|
|
|
|