Secondary LDAP directory
User names may be stored in a secondary LDAP directory, which can be different from the directory used for authentication.
Check Enable secondary LDAP server to display the configuration fields for a separate LDAP server.
When enabled, the search filter on the secondary LDAP directory can be used in Assign Access to authorize users or groups to access specific sessions. When this check box is cleared, the search filter option in the Assign Access is unavailable.
Enter the settings for your secondary LDAP server.
Select the type of LDAP server that is used to store user names. The options on this panel change depending on the LDAP server type you select. If you do not see your specific LDAP server in the list, select Generic LDAP Compliant Directory Server (RFC 2256).
Data can be passed between the MSS Administrative Server and the LDAP server as clear text or encrypted. The type of encryption used depends on your LDAP server. TLS is available for all server types, and Kerberos v5 is available for Windows Active Directory.
Plain Text. By default, Management and Security Server transmits data between the Administrative Server and the LDAP server in clear text. If you choose this option, you should prevent users from accessing the network link between these two servers.
TLS. When using TLS as the security option for an LDAP server, you must import the server’s trusted certificate. Use the IMPORT CERTIFICATE button (below). If you are presented with multiple certificates, it is best to import the CA certificate.
Kerberos v5. When you select Windows Active Directory with Kerberos, you must enter the name of the Kerberos key distribution centers. Multiple key distribution centers, delimited by commas or spaces, can be used. If you do not know the name of the Kerberos key distribution center, enter the fully-qualified DNS name of the Active Directory server.
The option under the key distribution center name field allows you to encrypt all data transmitted over the Kerberos connection. By default, only user names and passwords are passed securely between the Administrative and LDAP servers using Kerberos. Encrypting all data is more secure, but may increase performance overhead.
Enter the LDAP server name as either a name or a full IP address. When using TLS, this LDAP server name must exactly match the Common Name on the LDAP server's certificate.
Multiple server names, delimited by commas or spaces, can be used for failover support. If an LDAP server is down, the next server on the list will be contacted. In this case, all fields specified on this panel that are used for LDAP connections should be available on all the LDAP servers, and should have identical configurations.
Windows Active Directory - DNS domain. When Windows Active Directory is selected (without Kerberos), you have the option to use a DNS domain instead of a specific domain controller. No further configuration is required. For more information, see LDAP Configuration.
Enter the port used by your LDAP server. The default is 389 for plain text or 636 for TLS.
If you are using Active Directory, you may wish to set the server port to the global catalog port, which is 3268 (or 3269 over TLS). Global catalog searches can be faster than referral-based cross-domain searches.
Username and Password
Provide the username and password for an LDAP server account that can be used to access the directory in Read-only mode. Generally, the account does not require any special directory privileges but must be able to search the directory based on the most common directory attributes (such as
memberOf). Re-enter the password in the Password confirmation box.
The username must uniquely identify the user in the directory. The syntax depends on the type of LDAP server you are using.
For Windows Active Directory with Plain Text, enter
NetBIOS domain\sAMAccountName (such as
userPrincipalName (such as
distinguished name (such as
For any other LDAP server type, enter the distinguished name (such as
If this account password changes, be sure to update the account password here and apply the new settings. To avoid this problem, you may wish to set up an account that is not subject to automatic password aging policies, or that cannot be changed by other administrators without notice.
Directory search base. Enter the distinguished name of the node in the directory tree you want to use as the base for MSS Administrative Server search operations.
For more information about how to describe the search base, contact the LDAP administrator for your organization.
Click IMPORT CERTIFICATE to import the LDAP server's trusted certificate into the JRE's default trusted keystore. This button displays when TLS is selected.
Click TEST CONNECTION to verify that the secondary LDAP server can connect to the MSS Administrative Server.
It the test fails, consult the logs to resolve the issue.