Project

General

Profile

Actions
Copy link

Defect #8435

closed

LDAP authentification

Added by Ken Chan over 13 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
LDAP
Target version:
-
Start date:
2011-05-25
Due date:
% Done:

0%

Estimated time:
Resolution:
Invalid
Affected version:
1.1.3

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

Actions
Copy link
 #1

Updated by Etienne Massip over 13 years ago

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.

Actions
Copy link
 #2

Updated by Etienne Massip over 13 years ago

  • Category set to LDAP
Actions
Copy link
 #3

Updated by Ken Chan over 13 years ago

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".

Actions
Copy link
 #4

Updated by Etienne Massip over 13 years ago

  • Status changed from New to Closed
  • Resolution set to Invalid

Ok, so I can close this issue.

Actions
Copy link

Also available in: Atom PDF