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

dot in name ldap account #45

Open
MetallStill opened this issue Nov 30, 2016 · 1 comment
Open

dot in name ldap account #45

MetallStill opened this issue Nov 30, 2016 · 1 comment

Comments

@MetallStill
Copy link

Hi
If i create ldap user with name [email protected] i can sign in with ldap password one, two or more times. If i create [email protected] i can only one time sign in. on second time -
error: "Server application error" in browser (500)
into pdb -
django.db.utils.IntegrityError: duplicate key value violates unique constraint "users_user_email_243f6e77_uniq"
DETAIL: Key (email)=([email protected]) already exists.

veox added a commit to veox/taiga-contrib-ldap-auth-ensky that referenced this issue Dec 1, 2016
In `ldap_register()`, LDAP binding has already been performed,
and the user is allowed to authenticate. However, the current
logic is to look up the user entry in local DB using the string
from the login form. If the latter fails, creating a new user
is attempted - which might have been already created!

This still does not allow special characters (as in ensky#43, which
can be unsafe), but does address the underlying issue.

Should fix ensky#15, ensky#17, ensky#45, and make ensky#43 obsolete.
@veox
Copy link

veox commented Dec 1, 2016

Duplicate of #15.

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

No branches or pull requests

2 participants