LDAP authentication and sync

[multijob03]

Hi,
I configured the ldap authentication following this guide (http://www.ochounos.com/#blog/6). It imported in Alfresco all users from ldap, but I can't login in Alfresco with user/password stored in Ldap. There is no error in alfresco.log or catalina.out so I don't have any idea of why it doesn't work.
Also, I deleted in Alfresco one user imported from ldap and this user is not synchronized anymore (alfresco doesn't import it).
Do you have any idea of what could be the problem?


thanks

[mrogers]

The bits of the blog I looked at look o.k. 

[multijob03]

I compared the blog with the official docs and it seems fine. As I wrote, the sync worked (at least the first time), but I can't log in Alfresco with ldap users, just with users created directly in Alfresco: is there a setting to switch from "internal" authentication to ldap authentication?

[crosati]

I've the same problem. Fresh install of alfresco 4.2e on a centos 64. Then configured LDAP directly into the alfresco-global.properties

authentication.chain=alfrescoNtlm1:alfrescoNtlm,ldap1:ldap# This flag enables use of this LDAP subsystem for authentication. It may be# that this subsytem should only be used for synchronization, in which case# this flag should be set to false.ldap.authentication.active=true## This properties file brings together the common options for LDAP authentication rather than editing the bean definitions#ldap.authentication.allowGuestLogin=true# How to map the user id entered by the user to that passed through to LDAPldap.authentication.userNameFormat=uid=%s,ou=users,dc=armundia,dc=com# The LDAP context factory to useldap.authentication.java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory# The URL to connect to the LDAP server ldap.authentication.java.naming.provider.url=ldap://ldap…..com:389# The authentication mechanism to use for password validationldap.authentication.java.naming.security.authentication=simple# Escape commas entered by the user at bind time# Useful when using simple authentication and the CN is part of the DN and contains commasldap.authentication.escapeCommasInBind=false# Escape commas entered by the user when setting the authenticated user# Useful when using simple authentication and the CN is part of the DN and contains commas, and the escaped \, is # pulled in as part of an LDAP sync# If this option is set to true it will break the default home folder provider as space names can not contain \ldap.authentication.escapeCommasInUid=false# Comma separated list of user names who should be considered administrators by defaultldap.authentication.defaultAdministratorUserNames=….# This flag enables use of this LDAP subsystem for user and group# synchronization. It may be that this subsytem should only be used for # authentication, in which case this flag should be set to false.ldap.synchronization.active=true# The authentication mechanism to use for synchronizationldap.synchronization.java.naming.security.authentication=simple# The default principal to use (only used for LDAP sync)ldap.synchronization.java.naming.security.principal=cn\=ldap,dc\=armundia,dc\=com# The password for the default principal (only used for LDAP sync)ldap.synchronization.java.naming.security.credentials=…..# If positive, this property indicates that RFC 2696 paged results should be# used to split query results into batches of the specified size. This# overcomes any size limits imposed by the LDAP server.ldap.synchronization.queryBatchSize=0# If positive, this property indicates that range retrieval should be used to fetch# multi-valued attributes (such as member) in batches of the specified size.# Overcomes any size limits imposed by Active Directory.        ldap.synchronization.attributeBatchSize=0# The query to select all objects that represent the groups to import.ldap.synchronization.groupQuery=(objectclass\=groupOfNames)# The query to select objects that represent the groups to import that have changed since a certain time.ldap.synchronization.groupDifferentialQuery=(&(objectclass\=groupOfNames)(!(modifyTimestamp<\={0})))# The query to select all objects that represent the users to import.ldap.synchronization.personQuery=(objectclass\=inetOrgPerson)# The query to select objects that represent the users to import that have changed since a certain time.ldap.synchronization.personDifferentialQuery=(&(objectclass\=inetOrgPerson)(!(modifyTimestamp<\={0})))# The group search base restricts the LDAP group query to a sub section of tree on the LDAP server.ldap.synchronization.groupSearchBase=dc\=roles,dc\=alfresco,dc\=armundia,dc\=com# The user search base restricts the LDAP user query to a sub section of tree on the LDAP server.ldap.synchronization.userSearchBase=dc\=users,dc\=armundia,dc\=com# The name of the operational attribute recording the last update time for a group or user.ldap.synchronization.modifyTimestampAttributeName=modifyTimestamp# The timestamp format. Unfortunately, this varies between directory servers.ldap.synchronization.timestampFormat=yyyyMMddHHmmss'Z'# The attribute name on people objects found in LDAP to use as the uid in Alfrescoldap.synchronization.userIdAttributeName=uid# The attribute on person objects in LDAP to map to the first name property in Alfrescoldap.synchronization.userFirstNameAttributeName=givenName# The attribute on person objects in LDAP to map to the last name property in Alfrescoldap.synchronization.userLastNameAttributeName=sn# The attribute on person objects in LDAP to map to the email property in Alfrescoldap.synchronization.userEmailAttributeName=mail# The attribute on person objects in LDAP to map to the organizational id  property in Alfrescoldap.synchronization.userOrganizationalIdAttributeName=o# The default home folder provider to use for people created via LDAP importldap.synchronization.defaultHomeFolderProvider=largeHomeFolderProvider# The attribute on LDAP group objects to map to the authority name property in Alfrescoldap.synchronization.groupIdAttributeName=cn# The attribute on LDAP group objects to map to the authority display name property in Alfrescoldap.synchronization.groupDisplayNameAttributeName=description# The group type in LDAPldap.synchronization.groupType=groupOfNames# The person type in LDAPldap.synchronization.personType=inetOrgPerson# The attribute in LDAP on group objects that defines the DN for its membersldap.synchronization.groupMemberAttributeName=member# If true progress estimation is enabled. When enabled, the user query has to be run twice in order to count entries.ldap.synchronization.enableProgressEstimation=true# Requests timeout, in miliseconds, use 0 for none (default)ldap.authentication.java.naming.read.timeout=0‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I had no problem on the synchronization. After an alfresco restart i found all the users imported but it's impossible to login with them and there are no logs about it.

Anyone has resolved this issue ??

Thanks

[mrogers]

Looks o.k.  But the username format is suspicious.   Could you give examples of the userId in alfresco and the properties in ldap.  

[crosati]

In alfresco userid have the format first name letter "." lastname, foe exzmple mine is "c.rosati". I attach a screen shot of the relative ldap configuration which is not a really standart one (for what I'v understood).


Thanks for the help.

[eswbitto]

I ran into this same issue, but the cause for me was the SSL certificate/connection. I use centos 6.4 with Alfresco CE 4.2.d. I had to setup apache as the front end SSL connection to be able to actually log in with LDAP users. The tomcat certificate installation that is in the Alfresco documentation didn't help at all. So we opted to go the other route based on a fair amount of other Alfresco admin's have used this option as well.

[mrogers]

crosati

So if your user id in alfresco is c.rostati then I'd expect it to work.   But leave ldap.authentication.userNameFormat blank

If your user id in alfresco is your email address then you need to change ldap.synchronization.userIdAttributeName=mail

[crosati]

The problem was the ldap.authentication.userNameFormat, setting it to blank resolved the login issue.

Thanks.

[multijob03]

Putting the ldap.authentication.userNameFormat as blank worked for me too.

thanks a lot!