Hi

Compare your settings to the required backlogtool configuration file:

ldap.url=ldap://ldap.myhost.net:3268/
ldap.managerdn=xxxx
ldap.managerpassword=xxxx
ldap.user-search-filter=(sAMAccountName={0})
ldap.user-search-base=OU=Ewp,OU=Users

If we translate from your settings we get:
server => ldap.url
rootDN => ldap.user-search-base
userSearch => ldap.user-search-filter

Does that help?

Fredrik

from backlogtool.

Hi Fredrik,
Good day.
We have tried to use the one that you had provided and we still can't login with BacklogTool.

Ldap server settings:

ldap.url=ldap://xxx.com:389
ldap.managerdn=
ldap.managerpassword=
ldap.user-search-filter=(uid={0})
ldap.user-search-base=ou=People,ou=yyy.zzz

Stack trace:

org.springframework.ldap.NameNotFoundException: [LDAP: error code 32 - No Such Object]; nested exception is javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; remaining name ''
org.springframework.ldap.support.LdapUtils.convertLdapException(LdapUtils.java:174)
org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:306)
org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:259)
org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:606)
org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:524)
org.springframework.security.ldap.SpringSecurityLdapTemplate.searchForSingleAttributeValues(SpringSecurityLdapTemplate.java:173)
org.springframework.security.ldap.userdetails.DefaultLdapAuthoritiesPopulator.getGroupMembershipRoles(DefaultLdapAuthoritiesPopulator.java:215)
org.springframework.security.ldap.userdetails.DefaultLdapAuthoritiesPopulator.getGrantedAuthorities(DefaultLdapAuthoritiesPopulator.java:185)
org.springframework.security.ldap.authentication.LdapAuthenticationProvider.loadUserAuthorities(LdapAuthenticationProvider.java:197)
org.springframework.security.ldap.authentication.AbstractLdapAuthenticationProvider.authenticate(AbstractLdapAuthenticationProvider.java:63)
org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:156)
org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:174)
org.springframework.security.web.authentication.UsernamePasswordAuthenticationFilter.attemptAuthentication(UsernamePasswordAuthenticationFilter.java:94)
org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:194)
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:323)
org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105)
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:323)
org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87)
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:323)
org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:173)
org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346)
org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259)

Sincerely,
Gerald

from backlogtool.

Hi Gerald,

I guess you fixed the problem since you closed the issue. If not, make sure you use the full DN of the user on ldap.managerdn.
See this: http://stackoverflow.com/questions/4322289/ldap-search-by-persons-name-problem

Fredrik

from backlogtool.

Hi Fredrik,
Good day.
We just got the backtool working, here is the new ldap authentication settings we have

               <security:ldap-authentication-provider  
                user-search-filter="(uid={0})" 
                user-search-base="ou=People,ou=yyy.zzz"
                group-search-base="ou=People,ou=yyy.zzz"
                 />

We don't know why it is necessary to add the group-search-base for authentication.

Thanks
Gerald

from backlogtool.

Hi Gerald,
Thank you for reporting this. Good that you got it working!

From my experience I thought that the group-search-base was only needed for loading group authorities, which this tool does not use anyway. This could be a specific case with your LDAP server which we have not covered when testing with our own servers.

If more people are having the same problem, please report it here! Then we can change the configuration to cover the group-search-base as well.

Good luck with the tool!
Fredrik

from backlogtool.

Hi,

I just had the same Problem. And it worked with the group search entry. Thx for the workaround.

from backlogtool.

Hi,

I've got an LDAP auth issue too :-(

DEBUG: org.springframework.security.ldap.authentication.LdapAuthenticationProvider - Processing authentication request for user: uid=user1,ou=people,dc=metaverse,dc=fr
DEBUG: org.springframework.security.ldap.search.FilterBasedLdapUserSearch - Searching for user 'uid=user1,ou=people,dc=metaverse,dc=fr', with user search [ searchFilter: '(uid={0})', searchBase: 'ou=people', scope: subtree, searchTimeLimit: 0, derefLinkFlag: false ]
DEBUG: org.springframework.ldap.core.support.AbstractContextSource - Got Ldap context on server 'ldap://localhost:389/'
DEBUG: org.springframework.security.web.authentication.UsernamePasswordAuthenticationFilter - Authentication request failed: org.springframework.security.authentication.AuthenticationServiceException: [LDAP: error code 32 - No Such Object]; nested exception is javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; remaining name 'ou=people'
DEBUG: org.springframework.security.web.authentication.UsernamePasswordAuthenticationFilter - Updated SecurityContextHolder to contain null Authentication

I tried various inputs : uid=user1, uid=user1,dc=metaverse,dc=fr
same error : error code 32

using ldapsearch it works :
ldapsearch -x -b "uid=user1,ou=people,dc=metaverse,dc=fr"

extended LDIF
LDAPv3
base <uid=user1,ou=people,dc=metaverse,dc=fr> with scope subtree
filter: (objectclass=*)
requesting: ALL

user1, people, metaverse.fr
dn: uid=user1,ou=people,dc=metaverse,dc=fr
uid: user1
uidNumber: 1001
gidNumber: 1000
cn: User1
sn: User1
objectClass: top
objectClass: person
objectClass: posixAccount
objectClass: shadowAccount
loginShell: /bin/bash
homeDirectory: /home/user1

search result
search: 2
result: 0 Success

numResponses: 2
numEntries: 1

any idea ?

Note : I had to modify the log4.xml, by default it doesn't log this stuff...

from backlogtool.

Ok I fixed it..... but not sure it is the good solution...

1. I set the full ldpa url : ldap.url=ldap://localhost:389/dc=metaverse,dc=fr
2. I change the spring security params to

< security:authentication-manager >
< security:ldap-authentication-provider user-dn-pattern="uid={0},ou=people" >
< /security:ldap-authentication-provider >
< /security:authentication-manager >

as explained in : http://static.springsource.org/spring-security/site/docs/3.0.x/reference/ldap.html

then I login with : "user1"

from backlogtool.