Cannot See the LDAP Connection in the Organization Browser

The LDAP Connection shared resource may not be named correctly. The LDAP Connection must have the instance name in the format ldap/de/LDAPAlias.

This issue could also be a result of the LDAP Connection shared resource template configuration being incorrect. For example, the Provider URL or the Login Credentials specified in the LDAP Connection shared resource may be incorrect, or the resource template might not be scoped for the correct instance of the BPM application.

Procedure

  • Possible solutions are:
    • Rename the LDAP Connection resource instance.
    • Ensure that the LDAP shared resource template is configured properly.
    • Ensure that any unsafe characters in the URL are escaped. Unsafe characters should be represented by a special sequence of characters called escaping. For example, a space must be represented as %20. Thus, the DN ou=Product Development must be encoded as ou=Product%20Development.
Next topic: Troubleshooting LDAP Server Paging Errors
Previous topic: Cannot Log In as the User Mapped in the Organization Browser