-
Notifications
You must be signed in to change notification settings - Fork 17
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
Feature: Allow only one provider #46
Comments
You still need the button for that provider to let the users know what provider will be used to login. I think that the current approach is the best choice, though I don't think it's hard to create your own button which has already selected the provider. I think that a template to this button (with a template param to pick up the option) would be a welcomed option. PS. you still need the form to login, but it could be formatted as a single button..? |
We use a self hosted keycloak instance as identity provider together with the login-oauth2-extras plugin and do not let the user choose. With an option we set the provider to So maybe this is a very special use case where only a single provider is required. Maybe others are interested in this? |
Maybe help us to understand what you want by providing an image / screenshot? |
We have the use case where only a single provider is needed. We want to skip the provider's button and directly redirect to the provider.
We have added an option to change the flow without the post form in our own code and could provide an PR.
Is this a welcomed option for this plugin? Please, let me know.
The text was updated successfully, but these errors were encountered: