-
Notifications
You must be signed in to change notification settings - Fork 5
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
User accounts created in Decidim without going via Auth0 #51
Comments
There is no integration process with the invitation process and external authorisation providers currently. Workaround:
|
https://github.com/decidim/decidim/blob/v0.27.4/decidim-core/app/views/devise/mailer/invitation_instructions.html.erb email message is configured here. devise.mailer.invitation_instructions.hello as the variable email |
Actually i have implemented something like this on the other project i was working on. I have patched the app/views/devise/mailer/invitation_instructions.html.erb To redirect the user to a logged in page, so that the decidim auth system would redirect you to the right place. Beware there is an additional template app/views/devise/mailer/invitation_instructions.text.erb
|
@froger here's a possible solution :) |
When we invite people as a private member on an assembly and they get an email, it seems like when they click through it's creating them an account in Decidim without going through our auth system (Auth0) to log in first.
So when they next come to log in (eg when they don't have the cookie set, I assume) it's like they can't log in, as the account is present in Decidim but not in Auth0 which is the only way that you can log into our instance.
This is my best interpretation of the situation based on several people today having this problem (it's the last day of voting in our election so naturally the entire world is panic-voting at the last minute!)
Users who had this issue:
Nickname: alanhartless, prateekjain
Neither had a user in Auth0 but their accounts were registered in Decidim.
The text was updated successfully, but these errors were encountered: