2.8 Internal LDAP Server Guidelines and Settings

2.8.1 General Guidelines

Make sure that you don’t have trailing spaces after any of the values. For example,

  • Host URL: ldap://managed1.mosol.com:389

  • Base DN: ou=users,ou=acme corporation,dc=acme,dc=com

  • Filter: (objectclass=*)

  • Username Attribute: sAMAccountName

  • Principal: Change it to your network user name and password; for example:

    acme/jpeters, "password"

2.8.2 Non-SSL Settings

Make sure that you don’t have trailing spaces after any of the values. For example,

  • Host URL: ldap://acme1.acme.com:389

  • Authentication: simple

  • Security Protocol: none

2.8.3 SSL Settings

Make sure that you do not have trailing spaces after any of the values. For example,

  • Host URL: ldaps://acmecorp1.acme.com:636

  • Authentication: EXTERNAL

    Ensure that the remote LDAP server to which you want to connect supports this external method.

  • Security Protocol: ssl

Currently, we do not have an SSL-enabled LDAP server. You must get a signed certificate from the Active Directory* where you want to connect.

Use the following command to add the certificate to the JRE* under the Operations Center installation:

keytool -import -v -alias formula_ldap -file AD_cert -keypass changeit
   -keystore [location to 1.7 JRE cacerts, usually under OperationsCenter/bin]
   -storepass changeit

where AD_cert is the Active Directory certificate.

Use the following command to verify that the certificate has been installed:

keytool -list -keystore [location to 1.7 JRE cacerts, usually under OperationsCenter/bin]