|
|
|
@ -197,6 +197,7 @@ This specification defines the following login types:
|
|
|
|
|
- ``m.login.recaptcha``
|
|
|
|
|
- ``m.login.oauth2``
|
|
|
|
|
- ``m.login.email.identity``
|
|
|
|
|
- ``m.login.token``
|
|
|
|
|
- ``m.login.dummy``
|
|
|
|
|
|
|
|
|
|
Password-based
|
|
|
|
@ -228,6 +229,29 @@ To respond to this type, reply with an auth dict as follows::
|
|
|
|
|
"response": "<captcha response>"
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
Token-based
|
|
|
|
|
~~~~~~~~~~~
|
|
|
|
|
:Type:
|
|
|
|
|
``m.login.token``
|
|
|
|
|
:Description:
|
|
|
|
|
The client submits a username and token that was generated by the server.
|
|
|
|
|
|
|
|
|
|
To respond to this type, reply with an auth dict as follows::
|
|
|
|
|
|
|
|
|
|
{
|
|
|
|
|
"type": "m.login.token",
|
|
|
|
|
"user": "<user_id or user localpart>",
|
|
|
|
|
"token": "<token>",
|
|
|
|
|
"nonce": "<client generated nonce>"
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
The ``nonce`` should be a random string generated by the client for the
|
|
|
|
|
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
|
|
|
|
|
code.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
OAuth2-based
|
|
|
|
|
~~~~~~~~~~~~
|
|
|
|
|
:Type:
|
|
|
|
|