Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Small grammar fix. #2

Merged
merged 1 commit into from
Mar 27, 2020
Merged

Small grammar fix. #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ Even if identity providers were to provide site-specific data and directly ident

From a **usability perspective**, there are also some problems with federation:

- **The [NASCAR](https://developers.google.com/identity/toolkit/web/federated-login#the_nascar_page) screen**: every website has a different sign-in process and has to show a list of supported identity providers for the users to choose. The user is left to determine which identity provider to user, which one they may have used last time, what might happen if they pick a different IDP this time, and what what data might get shared, typically without any support from the browser in remembering the user’s past choice or highlight relevant options. We believe that, by pulling some of the responsibility for the browser, we can offer a personalized IDP disambiguation UI which can lead to higher conversion rates, but yet maintain user privacy.
- **The [NASCAR](https://developers.google.com/identity/toolkit/web/federated-login#the_nascar_page) screen**: every website has a different sign-in process and has to show a list of supported identity providers for the users to choose. The user is left to determine which identity provider to use, which one they may have used last time, what might happen if they pick a different IDP this time, and what what data might get shared, typically without any support from the browser in remembering the user’s past choice or highlight relevant options. We believe that, by pulling some of the responsibility for the browser, we can offer a personalized IDP disambiguation UI which can lead to higher conversion rates, but yet maintain user privacy.
- **Cumbersome navigation**: full page redirects take the user out of context of the site they were trying to use. IDPs also try using pop-up windows, but often because browsers are unaware of the use federation makes of popups, it has to apply a general rule across all usages, often blocking an IDP popup that would be otherwise helpful.

# Related Problems
Expand All @@ -64,4 +64,4 @@ Because cookies are not propagated across devices, a user has to sign back in (a

While this is still very much in formation and evolving rapidly, the following seems to be firm enough to serve as a baseline for discussion.

You can read more about in the [strawman proposal](proposal.md) document.
You can read more about in the [strawman proposal](proposal.md) document.