cancel
Showing results for 
Search instead for 
Did you mean: 

DN Component filter in ldap sychronization

wingtse
Champ in-the-making
Champ in-the-making
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?

thanks
-Wing
8 REPLIES 8

dward
Champ on-the-rise
Champ on-the-rise
Try

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

wingtse
Champ in-the-making
Champ in-the-making
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:

ouSmiley Very Happyepartments      
   ouSmiley Very Happyepartment1
      ou:User Accounts
      ouSmiley Frustratedystem Accounts (I need to filter this out)
   ouSmiley Very Happyepartment2
      ou:User Accounts
      ouSmiley Frustratedystem Accounts (I need to filter this out)
   ouSmiley Very Happyepartment3
      ou:User Accounts
      ouSmiley Frustratedystem Accounts (I need to filter this out)

dward
Champ on-the-rise
Champ on-the-rise
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)

wingtse
Champ in-the-making
Champ in-the-making
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

dward
Champ on-the-rise
Champ on-the-rise
This won't work in v3.2. And yes that is the correct LDAP syntax.

wingtse
Champ in-the-making
Champ in-the-making
Will this also be working on the coming 3.2 enterprise release? 
And when will the 3.2 enterprise going to be out?

-thanks

dward
Champ on-the-rise
Champ on-the-rise
Yes it will. I can't answer the other question but think it will be 'imminent'.

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

Tags


Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.