Project
TeamCity
Priority
Major
Type
Bug
State
Fixed
Assignee
Alexey Gopachenko
Subsystem
Server: Web: Administration
Affected versions
TeamCity 2.0 Agra (4111)
Fix versions
Agra Minor EAP (4161)
Fixed in build
17577  
  • Created by   Alexey Gopachenko
    4 years ago (17 Apr 2007 11:18)
  • Updated by   Alexey Gopachenko
    4 years ago (19 Apr 2007 04:20)
  • Jira: TW-2406
    (history, comments)
 
TW-2406 LDAP authenticator login format restriction should be configurable
0
Issue is visible to: All Users
  The issue is visible to the selected user group only
DOMAIN\sAMAccountName is not working with not AD-based envuronments

Issue wasresolved
Comments (3)
 
History
 
Linked Issues (?)
 
Alexey Gopachenko
  Alexey Gopachenko
17 Apr 2007 15:49
4 years ago
Added loginFilter property wich overrides default pattern.
Value is java.util.RegEx, tested for full match (loginFilter.matcher(login).matches())
Dmitri Colebatch
  Dmitri Colebatch
19 Apr 2007 04:19
4 years ago
This is my project that I'm using to connect to Novell eDirectory. It needs some more work to be configurable, but will work in the majority of cases.
Dmitri Colebatch
  Dmitri Colebatch
19 Apr 2007 04:20
4 years ago
This it the output of the other attachment. To use it, you need to put the following in your main-config.xml:

<auth-type>
<login-module class="au.com.toyota.isd.jetbrains.teamcity.auth.LDAPLoginModule" />
<login-description>Login using your LDAP credentials</login-description>
<guest-login allowed="true" />
</auth-type>

and in your ldap-config.properties have:

java.naming.provider.url=ldap://ldap-server/
java.naming.security.principal=<admin principal>
java.naming.security.credentials=<admin password>
java.naming.security.authentication=simple
java.naming.referral=follow