Configuring LDAP

After you install PowerVC, you can optionally configure it to work with an existing Lightweight Directory Access Protocol (LDAP) server.

Ensure that a supported LDAP server is installed and running in your environment if you plan to configure PowerVC with an LDAP server. See Hardware and software requirements for the list of supported LDAP servers. By default, PowerVC uses the local operating system to manage users and groups. See Configure operating system users and groups for details.

Notes:
  • You might need to configure the firewall to allow LDAP or LDAPS traffic.
  • Switching to LDAP restarts the HTTP service under which the identity service (Keystone) is running.
  • If SELinux is enabled and in enforcing mode, ensure that it does not prevent the httpd service from accessing the CA certificate file or directory that you specify.
  • LDAP servers typically limit the number of users and groups that can be returned for an LDAP query.This limit is configured on the LDAP server. Contact your LDAP administrator to obtain the current limit in your environment. It is highly recommended that appropriate user and group filters be part of your PowerVC LDAP configuration in order to limit the number of entities returned by LDAP searches and therefore avoid size limit errors.
  • Use port 636 to establish secure connection with the LDAP server.
Use the powervc-config identity repository command to configure LDAP or to switch back to using the local operating system. For instructions to use this command, run powervc-config identity repository --help. When you run this command, you must provide information about your LDAP configuration. Be sure to specify a user or a group for the initial administrator role assignment so that at least one user has administrator permissions. Administrators can then create additional role assignments as required.
Note: If you switch between using LDAP and the local operating system for your identity repository, all existing role assignments are removed because they apply to users and groups that are no longer available. For example, if you switch from the local operating system to LDAP, the users and groups that were defined in the local operating system do not exist in LDAP. Therefore, the role assignments do not exist in LDAP.

See Table 1 for the types of information you will need to obtain from your LDAP administrator. By default, the LDAP server is configured in secure mode.