-
Notifications
You must be signed in to change notification settings - Fork 47
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
Unable to Sign In with Keycloak - "Sign up closed" Error #1019
Comments
Hi @sigau , I think you need to add |
Hello |
Ah ok, those people need to log in using the old credentials and then use "Account connections" from the user menu (at /account/social/connections/). I think django-allauth has no means to connect those accounts automatically. This is probably also a security thing. Maybe @MyPyDavid has an idea? |
Thanks |
So we try and it's work ! But we're still open to know if it's possible to link existing account from the connection page ! (if it's not a security problem ) |
Yes, I guess depending on the amount of users you could also do this manually (assign a user to the social account in admin) or implement a custom adapter ( |
I think the main problem is that an automatic linking would allow people who control the email address, which might or might non be as protected as the password, to overtake existing accounts. I guess for your keycloak, you can assume that nobody can just take the email of someone else to create an account there. |
@MyPyDavid maybe your |
Hi,
We are trying to implement Keycloak for authentication on our instance of RDMO. Our
local.py
is configured as follows:We see the Keycloak logo on the connection page, and clicking on it successfully connects to Keycloak and returns to our RDMO instance. However, we receive the following message:
It seems we may have missed something in our
local.py
configuration, but we are unable to identify what is wrong.Do you have any suggestions on how to resolve this issue?
Thank you in advance,
Gautier
The text was updated successfully, but these errors were encountered: