Repository navigation
Replies: 2 comments 2 replies
|
I think that what you have described is the default behavior for most services. SSOs were created as a mechanism to allow a user to authenticate from one service to another without giving all services access to the user's authentication details. As such, when the user authenticates, they are redirected to the SSO's login page, an optional login screen is displayed (it may not show if the user is already authenticated), and then redirected back to the service they have accessed with a set of user info (or a code that can be used to access that info). Note that with this approach, all user authentication is handled on the SSO side (there are some exceptions to this, like the OIDC Direct Access Grant / Resource Owner Password Credentials Flow, but for the most part this is how things work). Because the service already has access to the user's information after the user presses the sign-in button for one of the SSO providers, there is no real reason why the service would not be able to create an account on the spot (provided that enough information is released). I was about to give GitLab (a service with multiple SSO options that came to mind) as an example, but they also have the SSO buttons on the sign-up page. However, other sites (e.g. Moodle or Microsoft - although their signup page is different) only have the SSO options on the login page, since creating an account as a separate step is not required. |
|
there's a workaround with Keycloakify https://docs.keycloakify.dev/faq/some-values-you-need-are-missing-from-in-kccontext |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I've set up keycloak with local users, with user registration enabled along with a couple of social media IdPs configured.
Like many online services, on my site I have both a Login and a Sign-Up button.
Yet, using the IdP buttons on the login form seems to also register a new user.
Am I thinking about this wrong? Shouldn't the IdP buttons also be available on the registration form? The default login form even contains "New User? Register" messaging at the bottom. Isn't a user is led to believe, falsely, that to register with my site they must create a local user account when really they could just auth with one of the social media IdPs?
I poked around in the flows trying to see if the IdPs could be added to the registration form, but to no avail. I saw in the login.ftl in the base theme where it's pretty much hardcoded there. So I'll need to do some advanced theming to address this? Or am I going about it wrong?
TIA
All reactions