LDAP issue with . in username
-
I’ve found out that when a user has a username like firstname.lastname and he logs in to Taiga, the Django backend says the username is firstnamelastname (so without the dot). This also means that logging in the second time doesn’t work.
-
Good catch! I can reproduce the issue. Until we know more, you can login to the admin/django interface of taiga and add that dot back for that user there. Then at least I was able to re-login as that user using the username with a dot. It also stays that way then.
-
Good catch! I can reproduce the issue. Until we know more, you can login to the admin/django interface of taiga and add that dot back for that user there. Then at least I was able to re-login as that user using the username with a dot. It also stays that way then.
@nebulon thanks! Indeed I did that also yesterday when a user urgently needed access and it worked.
-
Good catch! I can reproduce the issue. Until we know more, you can login to the admin/django interface of taiga and add that dot back for that user there. Then at least I was able to re-login as that user using the username with a dot. It also stays that way then.
@nebulon said in LDAP issue with . in username:
Good catch! I can reproduce the issue.
Just curious if there is any progress on this?
-
@nebulon said in LDAP issue with . in username:
Good catch! I can reproduce the issue.
Just curious if there is any progress on this?
@imc67 no update as such here, but I only now came around to create the upstream issue for this https://github.com/taigaio/taiga-front/issues/2250