Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-03-01 17:24:10 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Merge pull request #2042 from matrix-org/travis/1.0/ordered-flows

Browse source 
Clarify that login flows must be completed in order
This commit is contained in:
Travis Ralston 2019-05-29 16:26:22 -06:00 committed by GitHub
parent 4452ebf371 0580f51206
commit d2232aca97
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 2 deletions
Show stats 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.

6
specification/client_server_api.rst
View file

@ -406,8 +406,10 @@ 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. Failing to follow the flows in order must
result in an HTTP 401 response, as defined below. 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
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<