Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-9176: How to enable LDAP directory for IBM Tivoli LDAP server in Centrify Admin Portal

Centrify Identity Service, App Edition ,   Centrify Identity Service, App Plus ,   Centrify Privilege Service ,  

18 September,17 at 06:42 PM

Question:



How can an Administrator add an IBM Tivoli LDAP directory to the Centrify Admin portal/Which unique identifier is needed?




Answer:



By default, Centrify LDAP directory set up will use the unique identifiers are 'entryUuid' (for RFC-4530-compatible servers) and 'dominoUnid' (maintained for historical purposes).


Because there are several varieties of LDAP directories available, not all using the standard 'entryUuid' attribute, Centrify will need to specify on the backend, which unique attribute should be used.


To do this, the following steps should be used:

 
1. Determine the name(s) of the Bind that will be used in the Admin portal (ie. 'CompanyLdap')
2. Open a Support ticket with Centrify Support (support@centrify.com) and request that LDAP for IBM Tivoli will need to be configured to use unique Identifier "ibm-entryUuid" and include your tenant ID and pod (Found in Admin portal>Click Admin username in upper right and choose "About")
3. Support will have DevOps team add this config on the tenant backend
4. Once confirmed added (not before), next, configure LDAP and be sure to use the exact name provided to Support


ie. If the name will be 'CompanyLdap', the config should look as follows;


User-added image



Additionally, the signing cert used for the LDAP server will need to be installed on all Centrify Connector host machines that run the LDAP service, into the Computer Trusted Root Certificate Authorities store. 

 

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-6028: Getting Started with Office 365 and the Centrify Identity Service - Configuration Overview articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-3925: How to add Centrify parameter to a group policy articleKB-6041: How to show current license type in use by adclient? articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-4812: Getting Started with Centrify Identity Service articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out?