LDAP interface known issues

The following are the LDAP interface known issues:

  • Unix or Linux-based PAM authentication is not supported.
  • Ability to search on memberOf results in longer search times.
  • Support for TLS 1.2 only.
  • Only READ-only commands are supported. WRITE commands are not supported.
  • The server allows a page size of 1000 entries. If the size of the result exceeds the page size, an LDAP error code is returned. For a large result set, use Simple Pagination Control. See https://www.ietf.org/rfc/rfc2696.txt.
  • You must use an Okta user ID. If you are using samAccountName as a sign-in value for your apps, authentication fails.
  • For LDAP searches that query uniquemember and memberOf attributes, the LDAP Interface iterates through all pages before returning membership response back to the client.
  • LDAPi defines memberOf as a virtual operational attribute. It is returned only if :
    • memberOf is requested in the list of attributes, or
    • all operational attributes are requested using '+'

    Querying the memberOf attribute can affect your org rate limits. To avoid rate limit issues, Okta recommends using the group membership attribute uniqueMember. This configuration scales API calls with the number of groups and not the number of users.

    Improvements were also made to additional operational attributes that were part of LDAP core schema. This list includes hasSubordinatesstructuralObjectClass, entryDN, subschemaSubentry, and numSubordinates. Note that numSubordinates is not calculated for users and groups containers.

  • Sensitive attributes and LDAP Interface searches - LDAP Interface search filters that reference sensitive attributes or attributes that do not exist in the schema will not return any results.

    For example, if a custom attribute Employee Number is sensitive, then the filter employeenumber=123-45-6789 will not return any results, nor will the filter (|(employeenumber=*)(uniqueIdentifier=*).

    Additionally, LDAPi search filters that reference attributes that are not in the schema will not return any results. For example, if the attribute xyz does not exist in the schema, then the filter xyz=foo will not return any results, nor will the filter (|(xyz=*)(bar=*)).

  • When using Okta Verify multifactor authentication with the LDAP interface, the IP address reported will be the appserver IP rather than the client IP. This is due to limitations in being able to forward the client IP through LDAP.

  • The creation of Okta attributes such as user.uid is not supported. These attributes cannot be retrieved by <uid=user.login> attribute searches. Results are not returned when an attribute search is performed and the user profile contains the user.uid attribute.

  • Group administrators, help desk administrators, and custom administrators whose permissions are limited to viewing and managing the users of their assigned groups may experience a timeout when performing user searches.