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

Add support for "prompt=select_account" when using social sign-in #2709

Closed
3 of 6 tasks
jakhog opened this issue Sep 2, 2022 · 0 comments · Fixed by #3276
Closed
3 of 6 tasks

Add support for "prompt=select_account" when using social sign-in #2709

jakhog opened this issue Sep 2, 2022 · 0 comments · Fixed by #3276
Labels
feat New feature or request.

Comments

@jakhog
Copy link
Contributor

jakhog commented Sep 2, 2022

Preflight checklist

Describe your problem

It is common for our users to have multiple accounts in the social sign-in providers we use. Today (as far as I can tell) it is not possible to set the prompt parameter in the authentication requests. This means that in some situations, the users need to use different browsers or incognito mode to be able to sign in to our solution with the "correct" account.

Describe your ideal solution

We would like to be able to set prompt=select_account (as specified here: https://openid.net/specs/openid-connect-core-1_0.html#AuthRequest) parameter in the authentication requests for either a specific login flow, or a specific provider.

I see two ways of accomplishing this:

  1. Adding configuration for the social providers that support this prompt, so that it is set for all authentication requests.
  2. Adding another parameter in the initialise login flow requests /self-service/login/* (similar to refresh=true), then if it is supported by the provider - the prompt is set for only these requests.

For our case, I would be fine with setting it statically in the provider config - but you might have some ideas whether this would make sense on a per-login flow basis. Not all providers support this parameter, but I guess making it clear in the docs that it is a best-effort kind of thing should be fine.

Workarounds or alternatives

An alternative is to force the user to re-authenticate using the refresh=true parameter in the initiate login flow requests. This would allow the user to select the account, but also reduces the value of SSO by the provider.

Version

0.9.0

Additional Context

No response

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

Successfully merging a pull request may close this issue.

1 participant