MatrixSynapse/synapse
David Baker 8714ff6d51 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.

vector-im/riot-web#9586
2019-05-10 11:09:53 +01:00
..
_scripts
api Do checks on aliases for incoming m.room.aliases events (#5128) 2019-05-08 17:01:30 +01:00
app Merge pull request #5037 from matrix-org/erikj/limit_inflight_dns 2019-05-08 17:11:03 +01:00
appservice
config add options to require an access_token to GET /profile and /publicRooms on CS API (#5083) 2019-05-08 18:26:56 +01:00
crypto
events Do checks on aliases for incoming m.room.aliases events (#5128) 2019-05-08 17:01:30 +01:00
federation Run `black` on per_destination_queue 2019-05-09 16:27:02 +01:00
groups
handlers add options to require an access_token to GET /profile and /publicRooms on CS API (#5083) 2019-05-08 18:26:56 +01:00
http
metrics
module_api
push
replication
res/templates
rest Add a DUMMY stage to captcha-only registration flow 2019-05-10 11:09:53 +01:00
server_notices
state
static
storage Limit the number of EDUs in transactions to 100 as expected by receiver (#5138) 2019-05-09 11:01:41 +01:00
streams
util
__init__.py
event_auth.py
notifier.py
python_dependencies.py
secrets.py
server.py
server.pyi
types.py
visibility.py