topic Re: LDAP Synchronization with Alfresco 3.4d in Alfresco Archive

LDAP Synchronization with Alfresco 3.4d

pnavinkumar — Tue, 12 Apr 2011 05:41:45 GMT

Hi allI am new to alfresco and I am trying to setup the LDAP Sync with 3.4d. I have been able to establish the login to my AD which is a win2003 server. But somehow synchronization doesn't seem to work for me.Here is my configuration:authentication.chain=alfrescoNtlm1:alfrescoNtlm,ldap1:ldap-adldap.

Re: LDAP Synchronization with Alfresco 3.4d

goingcrazy — Wed, 13 Apr 2011 16:00:37 GMT

I too would like to know how to get LDAP synch to work- However I am using my CAS server for authentication… but I do wish to have my LDAP synching with Alfresco for the users

Re: LDAP Synchronization with Alfresco 3.4d

pnavinkumar — Tue, 26 Apr 2011 08:34:08 GMT

Members

Can anyone let me know a solution to this? I have been searching around for quite some time for a working solution but still haven't been able to figure out one.

Thanks for the help.

Navin

Re: LDAP Synchronization with Alfresco 3.4d

mouradef — Fri, 13 May 2011 14:15:00 GMT

Hi,
Did you resolve your problem ?
you still need help ?

Re: LDAP Synchronization with Alfresco 3.4d

mouradef — Fri, 13 May 2011 14:16:06 GMT

Hi,
Did you resolve your problem ?
you still need help ?

Re: LDAP Synchronization with Alfresco 3.4d

pnavinkumar — Mon, 16 May 2011 15:14:42 GMT

Hi

I haven't been able to get this resolved yet. Your help on this will be great. As I have told, I have been able to successfully login to the application using my AD credentials. But unable to synchronize the user and group info from AD LDAP.

Let me know if you would need any more info.

Thanks

Re: LDAP Synchronization with Alfresco 3.4d

mouradef — Tue, 17 May 2011 15:32:35 GMT

Hi,
I had the same problem before, LDAP connection was OK but i was unable to make full synchro
I resolved this by putting the following synchronization options in alfresco-globals.properties
synchronization.import.cron=15 * * * * ?
synchronization.synchronizeChangesOnly=false
synchronization.syncOnStartup=false

my experience is that these options are not taken into account when put in ldap-ad-authentification.properties.

ps: these options are for test purpose, to make full synchro every minute at 15 seconds, you certainly should tune it for your need

Tell me what do you think about this. Thanks.

Re: LDAP Synchronization with Alfresco 3.4d

pnavinkumar — Tue, 17 May 2011 16:11:22 GMT

Hi

I tried providing these settings on the alfresco.global properties file. But still i didn't work out for me. Can you share the ldap.synchronization settings that you had used with me?

Thanks

Re: LDAP Synchronization with Alfresco 3.4d

schulman — Wed, 18 May 2011 02:55:42 GMT

Hello,

I would change this :
ldap.synchronization.groupType=groupOfNames
by
ldap.synchronization.groupType=group

And
ldap.synchronization.timestampFormat=yyyyMMddHHmmss'Z'
by
ldap.synchronization.timestampFormat=yyyyMMddHHmmss'.0Z'

as mentionned here : http://wiki.alfresco.com/wiki/Alfresco_Authentication_Subsystems

Re: LDAP Synchronization with Alfresco 3.4d

mouradef — Wed, 18 May 2011 07:10:21 GMT

Hello,
this is my ldap-ad.properties file, located in: …subsystems/authetification/ldap-ad


# 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 taht passed through to LDAP

# In Active Directory, this can either be the user principal name (UPN) or DN.

# UPNs are in the form <sAMAccountName>@domain and are held in the userPrincipalName attribute of a user

ldap.authentication.userNameFormat=%s@yourDomain

 

# The LDAP context factory to use

ldap.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://yourServer

 

# The authentication mechanism to use for password validation

ldap.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 commas

ldap.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 default

ldap.authentication.defaultAdministratorUserNames=Administrator

 

# 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 synchronization

ldap.synchronization.java.naming.security.authentication=simple

 

# The default principal to bind with (only used for LDAP sync). This should be a UPN or DN

ldap.synchronization.java.naming.security.principal=cn\=****,OU\=****,OU\=***,DC\=****,DC\=**

 

# 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=1000

 

# 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=1000

 

# The query to select all objects that represent the groups to import.

ldap.synchronization.groupQuery=(objectclass\=group)

 

# The query to select objects that represent the groups to import that have changed since a certain time.

ldap.synchronization.groupDifferentialQuery=(&(objectclass\=group)(!(modifyTimestamp<\={0})))

 

# The query to select all objects that represent the users to import.

ldap.synchronization.personQuery=(&(objectclass\=user)(userAccountControl\:1.2.840.113556.1.4.803\:\=512))

 

# The query to select objects that represent the users to import that have changed since a certain time.

ldap.synchronization.personDifferentialQuery=(&(objectclass\=user)(userAccountControl\:1.2.840.113556.1.4.803\:\=512)(!(modifyTimestamp<\={0})))

 

# The group search base restricts the LDAP group query to a sub section of tree on the LDAP server.

#ldap.synchronization.groupSearchBase=CN=*****,OU=******,OU=****,OU=***,DC=***,DC=**

ldap.synchronization.groupSearchBase=OU=******,OU=****,OU=***,DC=***,DC=**
 

# The user search base restricts the LDAP user query to a sub section of tree on the LDAP server.

#users found in group search must belong to this userSearchBase

ldap.synchronization.userSearchBase=OU=**** , *****,OU=***,DC=****,DC=**

 

 

# 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'.0Z'

 

# The attribute name on people objects found in LDAP to use as the uid in Alfresco

ldap.synchronization.userIdAttributeName=sAMAccountName

 

# The attribute on person objects in LDAP to map to the first name property in Alfresco

ldap.synchronization.userFirstNameAttributeName=givenName

 

# The attribute on person objects in LDAP to map to the last name property in Alfresco

ldap.synchronization.userLastNameAttributeName=sn

 

# The attribute on person objects in LDAP to map to the email property in Alfresco

ldap.synchronization.userEmailAttributeName=mail

 

# The attribute on person objects in LDAP to map to the organizational id  property in Alfresco

ldap.synchronization.userOrganizationalIdAttributeName=company

 

# The default home folder provider to use for people created via LDAP import

ldap.synchronization.defaultHomeFolderProvider=userHomesHomeFolderProvider

 

# The attribute on LDAP group objects to map to the authority name property in Alfresco

ldap.synchronization.groupIdAttributeName=cn

 

# The attribute on LDAP group objects to map to the authority display name property in Alfresco

ldap.synchronization.groupDisplayNameAttributeName=displayName

 

# The group type in LDAP

ldap.synchronization.groupType=group

 

# The person type in LDAP

ldap.synchronization.personType=user

 

# The attribute in LDAP on group objects that defines the DN for its members

ldap.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
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: LDAP Synchronization with Alfresco 3.4d

pnavinkumar — Wed, 18 May 2011 09:11:30 GMT

Thanks for your help Mourad. I will try this out and let you know if this works for me.

Re: LDAP Synchronization with Alfresco 3.4d

pnavinkumar — Wed, 18 May 2011 13:21:45 GMT

Hi Mourad

I had tried but still it continues to give this error. Please do let me know if you are able to make some sense out of this.

18:47:15,151 Userystem INFO [security.sync.ChainingUserRegistrySynchronizer] Synchronizing users and groups with user registry 'ldap2'
18:47:15,151 Userystem WARN [security.sync.ChainingUserRegistrySynchronizer] Full synchronization with user registry 'ldap2'; some users and groups previously created by synchronization with this user registry may be removed.
18:47:15,151 Userystem INFO [security.sync.ChainingUserRegistrySynchronizer] Retrieving all groups from user registry 'ldap2'
18:47:15,151 Userystem ERROR [security.sync.ChainingUserRegistrySynchronizer] Synchronization aborted due to error
org.alfresco.error.AlfrescoRuntimeException: 04180005 User and group import failed
   at org.alfresco.repo.security.sync.ldap.LDAPUserRegistry.processQuery(LDAPUserRegistry.java:1141)
   at org.alfresco.repo.security.sync.ldap.LDAPUserRegistry.getGroups(LDAPUserRegistry.java:667)
   at org.alfresco.repo.security.sync.ChainingUserRegistrySynchronizer.syncWithPlugin(ChainingUserRegistrySynchronizer.java:618)
   at org.alfresco.repo.security.sync.ChainingUserRegistrySynchronizer.synchronize(ChainingUserRegistrySynchronizer.java:434)
   at org.alfresco.repo.security.sync.UserRegistrySynchronizerJob$1.doWork(UserRegistrySynchronizerJob.java:51)
   at org.alfresco.repo.security.authentication.AuthenticationUtil.runAs(AuthenticationUtil.java:508)
   at org.alfresco.repo.security.sync.UserRegistrySynchronizerJob.execute(UserRegistrySynchronizerJob.java:47)
   at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
   at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)
Caused by: javax.naming.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-031001CD, problem 2001 (NO_OBJECT), data 0, best match of:
   'DC=iTech,DC=com'
; remaining name 'ou=Groups,dc=iTech,dc=com'
   at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3066)
   at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2987)
   at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2794)
   at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1826)
   at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1749)
   at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:368)
   at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:338)
   at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:321)
   at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:248)
   at org.alfresco.repo.security.sync.ldap.LDAPUserRegistry.processQuery(LDAPUserRegistry.java:1129)
   … 8 more

If you notice the error above, it says
Caused by: javax.naming.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-031001CD, problem 2001 (NO_OBJECT), data 0, best match of:
   'DC=iTech,DC=com'

iTech.com is my domain name and I dont understand how it says there are no objects in this. Or does NameNotFoundException points to something else?

Thanks for your help.

Re: LDAP Synchronization with Alfresco 3.4d

pnavinkumar — Wed, 18 May 2011 13:35:49 GMT

Hi schulman

Both the settings are as you have mentioned for AD.

Re: LDAP Synchronization with Alfresco 3.4d

mouradef — Mon, 23 May 2011 09:35:47 GMT

Hi,
can you please post your ldap-authentification.properties ?

I had also problems in fetching users, it was because ldap.synchronization.userSearchBase was not correct.
Alfresco tried to retrieve users from this location. Are you sure your users belongs to value that you give to ldap.synchronization.userSearchBase ?

Re: LDAP Synchronization with Alfresco 3.4d

pnavinkumar — Mon, 23 May 2011 10:21:54 GMT

Hi

I have already given my ldap-configuration on the 1st post of this thread itself. I had given the usersearchbase to be CN\=Users,dc\=itech,dc\=com

Now based on the settings you had shared, I also tried ou\=User Accounts,dc\=iTech,dc\=com. I still have the same error. I have posted the error I am having on the previous posts. Please do let me know if you will need more information.

Thanks
Navin

Re: LDAP Synchronization with Alfresco 3.4d

mouradef — Mon, 23 May 2011 11:49:23 GMT

I think you have to add your domain name. Try replacing
ldap.authentication.userNameFormat=%s

by
ldap.authentication.userNameFormat=%s@itech.com

in my case, even if authentification is done using samacountname, i had to add domain name to make it work ! (don't understand why !)

Re: LDAP Synchronization with Alfresco 3.4d

pnavinkumar — Mon, 23 May 2011 12:11:10 GMT

Hi Mourad

I had tried with %s@itech.com sometime back itself and my current settings reflect that. But still there is no respite for me.

Anyways, I am planning to try and download 3.5d and try it on a new box altogether and see if I get any luck there. I did see a couple of posts where people had said it was working for them in 3.4c and it doesnt work in 3.4d. The solution was to move the authentication file from 3.4c machine to 3.4d machine.

By the way, which version are you working on?

Re: LDAP Synchronization with Alfresco 3.4d

mouradef — Mon, 23 May 2011 12:34:42 GMT

Hi Navin,
Sorry for not being able to help you.
I'm using Alfresco 3.4d and it's working well, after having many problemes, especially to correctly set usersearch and groupsearch
I started by a simple one group import, by setting :
ldap.synchronization.groupSearchBase=CN=OneGroup,ou\=Groups,dc\=itech,dc\=com

the idea is to ask alfresco to import one group (the one i explicitely give),
by giving the name of one group, i was sure group part is Ok and allows me to debug users import …divide and conquer

may be there is a bug somwhere, you can also move to 3.5 version and test
good luck

Re: LDAP Synchronization with Alfresco 3.4d

pnavinkumar — Mon, 23 May 2011 12:49:52 GMT

Hi

What is the UserSearchBase that you are currently using? I am connecting it to Windows 2003 AD server and using ldap-ad authentication subsystem for authentication.

Thanks

Re: LDAP Synchronization with Alfresco 3.4d

mouradef — Mon, 23 May 2011 12:57:26 GMT

my userSearchBase is like:
OU=MyDepartement,DC=TECH,DC=COM

i'm also using windows AD with ldap-ad authentification subsystem ..