Details

    • Type: Improvement
    • Status: Reopened
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: OpenIDM 6.0.0
    • Fix Version/s: None
    • Component/s: _Samples, UI
    • Labels:
    • Target Version/s:
    • Support Ticket IDs:

      Description

      When you use the Admin UI to create a provisioner file that uses the LDAP Connector against AD, The Admin UI creates the connector with the accountSearchFilter set to only find enabled accounts. The filter also uses objectClass type filters.

       

      Instead it should be checking against sAMAccountType.

       

      accountSearchFilter and accountSynchronizationFilter should be (sAMAccountType=805306368)

      groupSearchFilter and groupSynchronizationFilter should be (sAMAccountType=268435456)

       

      This is for two reasons.

       

      1. Most people are using the LDAP Connector against AD to provison, deprovison, and re-enable AD accounts. So, only seeing active accounts does not work for the majority of users.

       

      2. Using the sAMAccountType filters are more efficient in AD. Otherwise, a compound ldap filter is required which is less efficient. This is because computers in AD also have the objectClass user.

       

      The following Microsoft website's Note 1 mentions that it is better to use the sAMAccountType filter to find users.

       

      https://social.technet.microsoft.com/wiki/contents/articles/5392.active-directory-ldap-syntax-filters.aspx?Sort=MostRecent&PageIndex=1

       

      Please have the defaults generated by the Admin UI generate the sAMAccountType ldap filters.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mark.offutt Mark Offutt
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated: