Download Administrator Manual - Support
Transcript
7.3 Using An External LDAP Server For smaller clusters, a configuration where LDAP clients on all nodes point directly to the external server is recommended. An easy way to set this up is as follows: • On the head node: – the URIs in /etc/ldap.conf, and in the image file /cm/images/ default-image/etc/ldap.conf are set to point to the external LDAP server. – the updateprovisioners command (Section 6.1.4) is run to update any other provisioners. • Then, to update configurations on the regular nodes: – They can simply be rebooted to pick up the updated configuration. – Alternatively, to avoid a reboot, the imageupdate command (section 6.5.2) can be run to pick up the new image from a provisioner. • In the CMDaemon configuration file cmd.conf (Appendix C): – If another LDAP tool is to be used to manage external LDAP user management instead of cmgui or cmsh, then altering cmd.conf is not required. – If, however, system users and groups are to be managed via cmgui or cmsh, then CMDaemon, too, must refer to the external LDAP server instead of the default LDAP server on the head node. To set that up: * The LDAPHost, LDAPUser, LDAPPass, and LDAPSearchDN directives in cmd.conf are changed to refer to the external LDAP server. * CMDaemon is restarted to enable the new configurations. For larger clusters the preceding solution can cause issues due to traffic, latency, security and connectivity fault tolerance. If such occur, a better solution is to replicate the external LDAP server onto the head node, hence keeping all cluster authentication local, and making the presence of the external LDAP server unnecessary except for updates. This optimization is described in the next section. 7.3.1 External LDAP Server Replication This section explains how to set up replication for an external LDAP server to an LDAP server that is local to the cluster, if improved LDAP services are needed. Section 7.3.2 then explains how this can then be made to work with a high availability setup. Typically, the Bright LDAP server is configured as a replica (consumer) to the external LDAP server (provider), with the consumer refreshing its local database at set timed intervals. How the configuration is done varies according to the LDAP server used. The description in this section assumes the provider and consumer both use OpenLDAP. © Bright Computing, Inc. 125