Configuring an Authentication Backend

An LDAP server is required for TACACS+ authentication for external users and groups. Both LDAP over SSL (LDAPS) and LDAP over TLS are supported.

Configuration Steps

Follow these steps to configure an LDAP server:

  1. In the Cloudpath UI, go to TACACS+ > Authentication Backends The following screen is displayed.

    Adding an LDAP Authentication Server

  2. Click the Add LDAP Authentication Backend button.
  3. Configure the values to create the TACACS+ LDAP authentication backend, as shown in the following example.

    Creating the LDAP Authentication Backend
    screen updated for 5.9 with new field: "AD Group Prefix"

    • Authentication Backend Name: A descriptive name for the LDAP server; this name will be used when you build the configuration profile.
    • Description: (Optional) Description of the LDAP server.
    • LDAP Server Type: Choose one of the following from the drop-down list:
      • microsoft - for Active Directory
      • generic - for a generic LDAP where the user gets authenticated.
      • tacacs_schema - for a TACACS+ LDAP Schema.
      Note: The TACACS+ LDAP schema is not supported.
    • New field for 5.9
      AD Group Prefix (applicable only to AD Microsoft servers): An AD group name that contains this prefix is used to determine a user's TACACS+ group membership, and the prefix is stripped from the TACACS+ group name. Example: If the AD Group Prefix is set to "tacacs", members of the AD group called "TacacsNOC" get assigned to the TACACS+ group called "NOC".
      Note: TACACS+ group names are case-sensitive.
    • LDAP Host: Space-separated list of LDAP URLs, IP addresses, or hostnames, with the following guidelines:
      • For LDAP over SSL (LDAPS), always use ldaps://

        Example: ldaps://192.168.4.170:636

        Port 636 is the default for LDAPS.

      • For secure TLS, do not use ldaps:// in front of the IP address or hostname. If no port is specified, the default port 389 is used.

        Example: 192.168.4.170

      updated since last draft
    • Use StartTLS: Check this box only if you are using TLS. If checked, the server is required to support STARTTLS. An LDAP connection on port 389 will be an encrypted connection.
    • LDAP DN: Base DN of the LDAP server.
    • LDAP Scope: Choose one of the following from the drop-down list:
      • base - Search is performed only in the base entry.
      • one - Search is performed only on the children of the base entry.
      • sub - Search is perfromed on the base and all of its subordinates.
    • Bind Username: Username for LDAP bind.
    • Bind User Password: Password for the Bind Username.
  4. Click Save.

Adding the Certificate to Secure LDAP SSL or LDAP TLS Backend

new since last draft

Once you save the LDAP backend, you are returned to the main Authentication Backends screen. If you configured a secure backend (as shown in the SSL example in Creating the LDAP Authentication Backend

), you now must add the certificate:
Note: If you are not using a secure LDAP, you can proceed to the next section.

  1. Expand the arrow next to the secure LDAP to invoke the full view of the backend configuration:

    Backend Configuration From Which You Add the Certificate

  2. Click Add Certificate.
  3. On the ensuing screen, chose to “Pin the Certificate” and click Save.

Testing the LDAP Authentication

After you have added an LDAP backend (and the certificate if applicable), you can test the interaction with the backend by following the steps below:

  1. Click the green arrow for the LDAP backend you wish to test.
  2. In the ensuing screen, enter credentials for a user to verify interaction with the LDAP authentication backend, then click Continue.
  3. Check the results on the ensuing screen, an example of which is shown below.

    Authentication Test Results

    The "Result" field near the bottom of the screen can yield the following values:

    Possible Values for the "Result" field

    "Result" Field Value Meaning
    ERR LDAP connection error.
    Note: If you receive an error, check the following:
    • Use diagnostic tools (go to Support > Diagnostics) to ensure that you can successfully ping and perform a DNS Lookup on the LDAP backend.
    • Check your firewall requirements (go to Administration > Firewall Requirements).
    NFD LDAP user not found.
    NAK LDAP user found, but the password is incorrect or the user is not a member of any TACACS group.
    ACK LDAP user found and successfully authenticated.