synapse-product/synapse/rest/client
David Baker 085ae346ac Add a DUMMY stage to captcha-only registration flow
This allows the client to complete the email last which is more
natual for the user. Without this stage, if the client would
complete the recaptcha (and terms, if enabled) stages and then the
registration request would complete because you've now completed a
flow, even if you were intending to complete the flow that's the
same except has email auth at the end.

Adding a dummy auth stage to the recaptcha-only flow means it's
always unambiguous which flow the client was trying to complete.
Longer term we should think about changing the protocol so the
client explicitly says which flow it's trying to complete.

https://github.com/vector-im/riot-web/issues/9586
2019-05-10 10:52:24 +01:00
..
v1 add options to require an access_token to GET /profile and /publicRooms on CS API (#5083) 2019-05-08 18:26:56 +01:00
v2_alpha Add a DUMMY stage to captcha-only registration flow 2019-05-10 10:52:24 +01:00
__init__.py copyrights 2016-01-07 04:26:29 +00:00
transactions.py Port over enough to get some sytests running on Python 3 (#3668) 2018-08-20 23:54:49 +10:00
versions.py Allow "unavailable" presence status for /sync (#4592) 2019-02-08 21:09:56 +00:00