You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my organization, we are not using OU in AD. So in order to sync people to the right connection we have to use Ldap filter. But the LDAP filter is on LDAP settings page. Can it be a field on each location page?
This way the query for users are more flexible, and there are more options to have more correct results.
For example, when I query for people who is in my organization (we have others accounts for customers), with email @myorganizationDomain.com, and is at Denver location, and working in sales department.
If each of location setting page has a field called: LDAP String filter, then I think the LDAP search will be more accurate.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In my organization, we are not using OU in AD. So in order to sync people to the right connection we have to use Ldap filter. But the LDAP filter is on LDAP settings page. Can it be a field on each location page?
This way the query for users are more flexible, and there are more options to have more correct results.
For example, when I query for people who is in my organization (we have others accounts for customers), with email @myorganizationDomain.com, and is at Denver location, and working in sales department.
If each of location setting page has a field called: LDAP String filter, then I think the LDAP search will be more accurate.
What do you think?
Beta Was this translation helpful? Give feedback.
All reactions