archive
/
matrix-spec
mirror of https://github.com/matrix-org/matrix-spec
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix minor grammatical fixes.

Browse Source 
Co-Authored-By: Hubert Chathi <hubert@uhoreg.ca>
pull/977/head
Patrick Cloke 5 years ago committed by GitHub
parent 4cfcda57fb
commit f6879c897b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File

6
proposals/2454-ui-interactive-auth-for-sso.md
Unescape Escape View File

@ -13,7 +13,7 @@ we need to delegate that check to the SSO system.
At the protocol level, this means adding support for SSO to the At the protocol level, this means adding support for SSO to the
[user-interactive authentication API](https://matrix.org/docs/spec/client_server/r0.6.0#user-interactive-authentication-api). [user-interactive authentication API](https://matrix.org/docs/spec/client_server/r0.6.0#user-interactive-authentication-api).
In theory, once SSO is added as a possible flow for authentication any clients In theory, once SSO is added as a possible flow for authentication, any clients
that already implement the [fallback process for unknown authentication types](https://matrix.org/docs/spec/client_server/r0.6.0#fallback) that already implement the [fallback process for unknown authentication types](https://matrix.org/docs/spec/client_server/r0.6.0#fallback)
will work fine without modification. It is unknown whether this is widely will work fine without modification. It is unknown whether this is widely
supported among clients. supported among clients.
@ -24,7 +24,7 @@ An [additional authentication type](https://matrix.org/docs/spec/client_server/r
of `m.login.sso` is added to the user-interactive authentication specification. of `m.login.sso` is added to the user-interactive authentication specification.
There are no additional parameters as part of this authentication type. As per There are no additional parameters as part of this authentication type. As per
the user-interactive authentication specification the only parameter include in the user-interactive authentication specification, the only parameter included in
the `auth` dictionary should be the session ID from the homeserver, e.g.: the `auth` dictionary should be the session ID from the homeserver, e.g.:
```json ```json
@ -57,7 +57,7 @@ When choosing this authentication flow, the following should occur:
3. The SSO provider validates the user, and redirects the browser back to the 3. The SSO provider validates the user, and redirects the browser back to the
homeserver. homeserver.
4. The homeserver validates the response from the SSO provider, updates the 4. The homeserver validates the response from the SSO provider, updates the
user-interactive auth session to show that the SSO has completed, user-interactive auth session to show that the SSO has completed, and
[serves the fallback auth completion page as specced](https://matrix.org/docs/spec/client_server/r0.6.0#fallback). [serves the fallback auth completion page as specced](https://matrix.org/docs/spec/client_server/r0.6.0#fallback).
5. The client resubmits its original request, with its original session id, 5. The client resubmits its original request, with its original session id,
which now should complete. which now should complete.

Write Preview
Loading…
Cancel
Save