cancel
Showing results for 
Search instead for 
Did you mean: 

Problem to connect LDAP-AD avec Alfresco 3.3

soriaedu79
Champ in-the-making
Champ in-the-making
Hello,

I'm doing a migration from 3.1 to 3.3 and I can't to connect to the AD. In the version 3.1 it worked fine.

My properties are:


ldap.authentication.active=true
ldap.authentication.userNameFormat=samaccountname=%s
ldap.authentication.java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
ldap.authentication.java.naming.provider.url=ldap://myserver:389
ldap.authentication.java.naming.security.authentication=simple
ldap.authentication.escapeCommasInBind=false
ldap.authentication.escapeCommasInUid=false
ldap.synchronization.active=false

I have activate the property:

log4j.logger.org.alfresco.repo.security.authentication=debug

I get an exception 525 (User doesn't exist)

15:44:02,652 DEBUG [org.alfresco.repo.security.authentication.ldap.LDAPAuthenticationComponentImpl] Failed to authenticate user "user1"
org.alfresco.repo.security.authentication.AuthenticationException: 06050005 LDAP authentication failed.
   at org.alfresco.repo.security.authentication.ldap.LDAPInitialDirContextFactoryImpl.buildInitialDirContext(LDAPInitialDirContextFactoryImpl.java:110)

Caused by: javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 525, vece]
   at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3005)


I have tested also with the line


ldap.authentication.userNameFormat=%s

but it didn't work.

Actually I have to make authentication and synchronization but I want to check the authentication first.

Any idea?
5 REPLIES 5

boutch55555
Champ in-the-making
Champ in-the-making
can you ping the ldap server (myserver from youn config) from the alfresco server ?

altroz
Champ in-the-making
Champ in-the-making
have you try this:
ldap.authentication.userNameFormat=%s@yourdomain.com

soriaedu79
Champ in-the-making
Champ in-the-making
Yes, the ping works fine.

I have tested the new userNameFormat (%s@yourdomain.com) and it didn't work Smiley Sad

It's really strange because the same parameters for the version 3.1 were OK.

Other ideas?

Thank you in advance

soriaedu79
Champ in-the-making
Champ in-the-making
I'm sorry.

Actually with the userNameFormat (%s@yourdomain.com) it works perfectly!!

Thank you so much

altroz
Champ in-the-making
Champ in-the-making
Smiley Very Happy you owe me a beer Smiley Wink cheers!