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

Add more explanation

Browse Source
pull/977/head
Michael Telatynski 4 years ago
parent 8ac23599b2
commit 153c55788d
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File

5
proposals/2858-Multiple-SSO-Identity-Providers.md
Unescape Escape View File

@ -12,7 +12,10 @@ Currently, Matrix supports `m.login.sso`, `m.login.token` and `/login/sso/redire
pass their user to the configured Identity provider and for them to come back with something which pass their user to the configured Identity provider and for them to come back with something which
is exchangeable for a Matrix access token. This flow offers no insight to the user as to what is exchangeable for a Matrix access token. This flow offers no insight to the user as to what
Identity providers are available. It allows clients to offer a super generic `Sign in with SSO` Identity providers are available. It allows clients to offer a super generic `Sign in with SSO`
button only. button only. With the currently possible solutions and workarounds the experience is far from great
and user's have to blindly click `Sign in with SSO` without any clue as to what's hiding on the other
side of the door. Some users will definitely not be familiar with `SSO` but will be with the concept of
"Continue with Google" or similar.
By augmenting the `m.login.sso` flow discovery definition to include metadata on the supported IDPs By augmenting the `m.login.sso` flow discovery definition to include metadata on the supported IDPs
the client can show a button for each of the supported providers, yielding a much more usable the client can show a button for each of the supported providers, yielding a much more usable

Write Preview
Loading…
Cancel
Save