topic Re: DN Component filter in ldap sychronization in Alfresco Archive

DN Component filter in ldap sychronization

wingtse — Mon, 07 Dec 2009 21:59:13 GMT

Is DN Component filter not supported on 3.2 for personQuery?I wanted basically only import user who is under the ou "User Accounts"When i do this, it didn't return any user at all.ldap.synchronization.personQuery=(&(objectclass\=user)(ou\:dn\:\=User Accounts))Anyone know what could be wrong?than

Re: DN Component filter in ldap sychronization

dward — Mon, 07 Dec 2009 22:17:38 GMT

Try

ldap.synchronization.userSearchBase=ou=User Accounts,dc=company,dc=com

Re: DN Component filter in ldap sychronization

wingtse — Mon, 07 Dec 2009 22:55:55 GMT

I can't

I have to keep the
ldap.synchronization.userSearchBase=ou=Departments,dc=company,dc=com

Because the ou "User Accounts" is other other ou….
I have a hierarchy like following:

ouepartments
   ouepartment1
      ou:User Accounts
      ouystem Accounts (I need to filter this out)
   ouepartment2
      ou:User Accounts
      ouystem Accounts (I need to filter this out)
   ouepartment3
      ou:User Accounts
      ouystem Accounts (I need to filter this out)

Re: DN Component filter in ldap sychronization

dward — Tue, 08 Dec 2009 09:53:03 GMT

In that case you need

ldap.synchronization.userSearchBase=ou=Departments,dc=company,dc=com
ldap.authentication.userNameFormat=# Keep this blank to allow dynamic DN resolution under multiple OUs
ldap.synchronization.personQuery=(&(objectclass\=inetOrgPerson)(ou\=User Accounts))
ldap.synchronization.personDifferentialQuery=(&(objectclass\=inetOrgPerson)(ou\=User Accounts)(!(modifyTimestamp<\={0})))‍‍‍‍

Make sure you are using release 3.2r2 or later, which supports the dynamic DN resolution (DNs are resolved from a search rather than userNameFormat)

Re: DN Component filter in ldap sychronization

wingtse — Tue, 08 Dec 2009 15:25:38 GMT

It doesn't work, we have 3.2 (r 2384)
Is this how we suppose to search for dn component in Alfresco (ou\=User Accounts)?
Because i LDAP the search should be (ou\:dn\:\=User Accounts)

thanks
-Wing

Re: DN Component filter in ldap sychronization

dward — Tue, 08 Dec 2009 15:29:35 GMT

This won't work in v3.2. And yes that is the correct LDAP syntax.

Re: DN Component filter in ldap sychronization

wingtse — Tue, 08 Dec 2009 15:35:49 GMT

Will this also be working on the coming 3.2 enterprise release?
And when will the 3.2 enterprise going to be out?

-thanks

Re: DN Component filter in ldap sychronization

dward — Tue, 08 Dec 2009 15:58:38 GMT

Yes it will. I can't answer the other question but think it will be 'imminent'.

Re: DN Component filter in ldap sychronization

wingtse — Wed, 23 Dec 2009 17:35:02 GMT

we just installed 3.2E and the the dynamic DN resolution using ldap.synchronization.personQuery=(&(objectclass\=inetOrgPerson)(ou\=User Accounts)) still doesn't work