From ba3e204a4840e84619b6c6a0ba4c0a6fbfa3536b Mon Sep 17 00:00:00 2001 From: Michael Telatynski <7t3chguy@gmail.com> Date: Mon, 1 Mar 2021 22:25:45 +0000 Subject: [PATCH] Update proposals/2858-Multiple-SSO-Identity-Providers.md Co-authored-by: Matthew Hodgson --- proposals/2858-Multiple-SSO-Identity-Providers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/2858-Multiple-SSO-Identity-Providers.md b/proposals/2858-Multiple-SSO-Identity-Providers.md index c12e5ab9..298911b1 100644 --- a/proposals/2858-Multiple-SSO-Identity-Providers.md +++ b/proposals/2858-Multiple-SSO-Identity-Providers.md @@ -10,7 +10,7 @@ pass their user to the configured Identity provider and for them to come back wi is exchangeable for a Matrix access token. This flow offers no insight to the user as to what Identity providers are available: clients can offer only a very generic `Sign in with SSO` button. 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 +and users 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.