nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

DN Component filter in ldap sychronization

wingtse

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

Find more posts tagged with

Comments

dward

Try

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

wingtse

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:

ou

epartments
ou

epartment1
ou:User Accounts
ou

ystem Accounts (I need to filter this out)
ou

epartment2
ou:User Accounts
ou

ystem Accounts (I need to filter this out)
ou

epartment3
ou:User Accounts
ou

ystem Accounts (I need to filter this out)

dward

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

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

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

wingtse

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

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

wingtse

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