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.

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

Access to FedCM available options (suitable to site) #451

Open
Bojhan opened this issue Mar 30, 2023 · 1 comment
Open

Access to FedCM available options (suitable to site) #451

Bojhan opened this issue Mar 30, 2023 · 1 comment

Comments

@Bojhan
Copy link

Bojhan commented Mar 30, 2023

In the current Seamless Access implementation, we use a Seamless Access cookie to allow for the "Access button" to be pre-populated with the latest chosen institute. This allows for cross-domain ease of use.

It was marked that FedCM would beyond its authentication case, provide a potential solution for this. Is it possible to pre-populate with a identity provider from the FedCM list (and potentially match against accepted identity providers) - when there has not yet been an association to a identity.

This would be similar to pre-populating the Google sign-in button on a site, with the name of a FedCM already used profile.

@npm1
Copy link
Collaborator

npm1 commented Mar 30, 2023

It was marked that FedCM would beyond its authentication case, provide a potential solution for this. Is it possible to pre-populate with a identity provider from the FedCM list (and potentially match against accepted identity providers) - when there has not yet been an association to a identity.

It would be a leak of information for a site that has not engaged with the user to be able to query the last IDP used by the user. Any ideas on how we can achieve your use-case without this leak?

This would be similar to pre-populating the Google sign-in button on a site, with the name of a FedCM already used profile.

It is different in the sense that this feature requires knowing some user information before FedCM has been used on the site, whereas for the personalized buttons we are supporting this only when FedCM has been used in this site in the past.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants