4.4 Configuring LDAP

You can configure a Change Guardian server for LDAP authentication to enable users to log in to Change Guardian with their LDAP directory credentials. With LDAP, Change Guardian processes each user group in a policy as group members.

Following sections provide information about configuring LDAP:

4.4.1 Configuring LDAP for Authentication

You can perform LDAP authentication by either using an SSL connection or by using an unencrypted connection to the LDAP server. You can configure the Change Guardian server for LDAP authentication with or without using anonymous search on the LDAP directory:

  • Anonymous: When you create Change Guardian LDAP user accounts, specify the directory user name. However, you do not have to specify the user distinguished name (DN).

    When an LDAP user logs in, the Change Guardian server performs an anonymous search on the LDAP directory based on the specified user name. The Change Guardian server finds the corresponding DN and then authenticates the user against the LDAP directory by using the user DN.

  • Non Anonymous: When you create Change Guardian LDAP user accounts, you must specify the user DN along with the user name.

    When an LDAP user logs in, the Change Guardian server authenticates the user against the LDAP directory by using the specified user DN.

NOTE:If anonymous search is disabled on the LDAP directory, you must not configure the Change Guardian server to use anonymous search.

Setting up LDAP Authentication

To set up LDAP authentication:

  1. Log in to the Administration Console, click Users > LDAP Settings.

  2. Specify the options to configure LDAP authentication:

    Host: Hostname or IP address for SSL connections.

    SSL: SSL connection to the LDAP server.

    Port: Port for the SSL connection. The default SSL port number is 636 and the default non-SSL port number is 389.

    Certificate File Path: The path of the CA certificate file for the LDAP server.

    Specify the certificate file path when you are using an SSL connection, and if the LDAP server certificate is not signed by a well-known CA and is not trusted by default.

    Anonymous Search: Option to perform anonymous searches or non-anonymous searches on the LDAP directory.

    Base DN: The root container to search for users.

    For example. set o=netiq for eDirectory.

    For anonymous search, specify the root container of the LDAP directory. This is optional for eDirectory, but mandatory for Active Directory. For eDirectory, if you do not specify the Base DN, Change Guardian searches the entire directory to locate the users.

    For non-anonymous search, specify the root container in the LDAP directory that contains users. This is mandatory if you are using Active Directory and if you set a domain name.

    Search Attribute: The LDAP attribute having the user name to search for users.

    For example, the search attribute for eDirectory is uid and for Active Directory it is sAMAccountName.

    Domain Name: The Active Directory domain.

    Change Guardian can perform anonymous search in Active Directory. Change Guardian uses the username@domainname (userPrincipalName) to authenticate the user before searching for the LDAP user object.

    NOTE:If Base DN is set and Domain Name is not set, the Base DN is appended to the relative user DN to construct the absolute user DN.

    For example, if the Base DN is set to o=netiq and the absolute user DN is cn=sentinel_ldap_user,o=netiq, Change Guardian uses the relative user DN cn=sentinel_ldap_user when you create an LDAP user account.

  3. Click Test Connection to test the LDAP connection.

    • Specify the domain name and password if you did not specify earlier. The user DN can be relative to the Base DN.

    • According to LDAP standards, when you use reserved special characters as literals in a User DN, you must use \. eDirectory or Active Directory might require additional escape characters. You must use \ as the escape character for the following scenarios:

      • A space or # occurring at the beginning of the string

      • A space occurring at the end of the string

      • Any one of the following characters: +, ", \, <, >, or ;

        For example, if the User DN contains a comma as a literal, specify the User DN as follows:

        CN=Test\,User,CN=Users,DC=netiq,DC=com

    If there is an error, review the configuration details you provided and test the connection again. To learn about the errors, examine the /var/opt/novell/sentinel/log/server0.0.log file.

    NOTE:You must ensure that the test connection is successful before saving the LDAP settings.

  4. Click Save to save the LDAP settings.

    Verify the configuration:

    • Check that the LdapLogin section in the /etc/opt/novell/sentinel/config/auth.login file is updated. For example:

      LdapLogin {
              com.sun.security.auth.module.LdapLoginModule required
      java.naming.ldap.factory.socket="com.esecurity.common.communication.ProxyLdapSSLSocketFactory"
              userProvider="ldap://10.0.0.1:636/o=netiq"
              userFilter="(&(uid={USERNAME})(objectclass=user))"
              useSSL=true;
      };
    • If you provided the LDAP server CA certificate, it is added to the /etc/opt/novell/sentinel/config/.ldapkeystore.jks keystore.

After saving the LDAP settings successfully, you can create LDAP user accounts to enable users to log in to Change Guardian by using their LDAP directory credentials.

NOTE:You can also configure the Change Guardian server for LDAP authentication by running the ldap_auth_config.sh script in the /opt/novell/sentinel/setup directory.

The script also supports command line options. To view the options, run the script as follows:

/opt/novell/sentinel/setup/ldap_auth_config.sh --help 

Logging in Using LDAP User Credentials

After configuring the Change Guardian server for LDAP authentication, create Change Guardian LDAP user accounts and log in to Change Guardian by using your LDAP user name and password. For more information about creating LDAP user accounts, see Creating Users.

4.4.2 Configuring LDAP to Access Domain Controller

To access and configure the domain controller in LDAP settings:

  1. In Policy Editor, click Settings > LDAP Settings.

  2. In the LDAP Settings window, click New.

  3. Specify the following fields:

    Domain name: Name of the Active Directory domain.

    For example, test.example.com

    User name: Name of the Active Directory user name.

    You can specify the user name in the following format:

    • <user_name>

    • <domain_name\user_name>

    • <user_name@domain_name.com>

    Password: Password for the Active Directory user.

    Polling interval: The interval at which the Change Guardian server synchronizes all objects and entities with Active Directory configuration.

  4. Click Test to test the authentication of the Active Directory user before searching for the LDAP object.

  5. Click Apply to save the configuration.

The LDAP Settings window displays the domain name for each resource. In this window, you can also edit and delete settings.

NOTE:You cannot delete a setting that an active policy is using.