Using built-in authentication, you create users, set passwords, assign users to groups and manage groups using the CLC Server web administrative interface or a CLC Workbench. All the user information is stored on the CLC Server and is not accessible from other systems.
Using the LDAP directory option, information needed during authentication and group memberships is retrieved from the specified LDAP directory (figure 4.3).
Encryption The default is Plain text, with options available for encryption using Start TLS ("Forced Start TLS") or LDAP over SSL ("ldaps://").
DN to use for lookups This allows you to choose which bind should be used for read and search operations. If no bind DN have been entered an unauthenticated bind will be used to do the initial lookup (lookup of users DN based on the username), and all other read and search operations will be performed with users binds. If the Bind DN and Bind password have been filled in, you have the choice between using the 'Bind DN' or the 'User DN' for read and search operations, the 'Bind DN' will in this case always be used for the initial lookup.
User object class and Group object class Intended for use where the standard posixAccount and posixGroup classes are not appropriate.
Kerberos/GSSAPI Authentication Enable the LDAP integration to use Kerberos/GSSAPI.
CLC_SERVER_BASE/jre/bin/keytool -import -alias \ ldap_certificate -file LDAP_CERTIFICATE.cer -keystore \ CLC_SERVER_BASE/jre/lib/security/cacerts -storepass changeitReplace LDAP_CERTIFICATE with the path to the certificate your LDAP server uses for Start TLS/LDAPS connections. Replace CLC_SERVER_BASE with the path to the servers installation location.
For a node setup, this must be done for all job nodes as well.
Caution: If you update the server installation or reinstall the server, all imported certificates will be removed, and have to be imported again. You should also be aware that certificates have an expiration date, and will not be trusted after this date. Make sure to add a new certificate in advance of the expiration date.
Using the Active Directory option, information needed during authentication and group memberships is retrieved from the specified Active Directory. Encryption options (Start TLS and LDAP over SSL) are available (figure 4.4).
Hostname We recommend entering a Global Catalog in the hostname field. This avoids the CLC Server being redirected to several different Domain Controllers to obtain information about users and groups, and can thereby speed up the response time considerably in complex network environments. When a Global Catalog is specified, the port number must be configured to either
- 3268 LDAP, plain/startTLS, comparable to port 389, or
- 3269 LDAPS, SSL, comparable to 636
Please see the notes in the LDAP section for other recommendations and configuration details.