Defect #8435
closed
Added by Ken Chan over 13 years ago.
Updated over 13 years ago.
Description
I find that the LDAP authentification sometimes works and sometimes fails when I user sAMAccoutName attribute to verify the account. However, when I use userPrincipalName attribute as the user logon, it works.
By the way, I am using Active Directory on Windows Server 2003
If you think this is a Redmine bug, please provide all details (what means "fail" ??) (see SubmittingBugs).
BTW, I don't think it is, as I'm using RM against AD on WS2003 too and have no problem with sAMAccountName.
The LDAP authentication fails when I allow user to create accounts on the fly.
After trial and error, I found out the LDAP authentication actually does not fail. I also found out that "The user is invalid" because there is already user with the same log-on name in Redmine. This prevents creation of account on the fly, hence generate the "the user is invalid".
- Status changed from New to Closed
- Resolution set to Invalid
Ok, so I can close this issue.
Also available in: Atom
PDF