wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Clarify that login flows must be completed in order

Browse source 
Fixes https://github.com/matrix-org/matrix-doc/issues/1134

Evidence of this being the case is shown here: https://github.com/matrix-org/synapse/pull/5174
This commit is contained in:
Travis Ralston 2019-05-27 23:15:02 -06:00
parent 699cafe670
commit 572a6056ad
2 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

1
changelogs/client_server/newsfragments/2042.clarification Normal file
View file

@ -0,0 +1 @@
Clarify that login flows are meant to be completed in order.

5
specification/client_server_api.rst
View file

@ -406,8 +406,9 @@ an additional stage. This exchange continues until the final success.
For each endpoint, a server offers one or more 'flows' that the client can use For each endpoint, a server offers one or more 'flows' that the client can use
to authenticate itself. Each flow comprises a series of stages, as described to authenticate itself. Each flow comprises a series of stages, as described
above. The client is free to choose which flow it follows. When all stages in a above. The client is free to choose which flow it follows, however the flow's
flow are complete, authentication is complete and the API call succeeds. stages must be completed in order. When all stages in a flow are complete,
authentication is complete and the API call succeeds.
User-interactive API in the REST API User-interactive API in the REST API
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<