Legal Disclaimer: The resource assets in this website may include abbreviated and/or legacy terminology for HPE Aruba Networking products. See www.arubanetworks.com for current and complete HPE Aruba Networking product lines and names.
Preparing Policy Manager for LDAP and SQL Authentication Sources
This section describes how to prepare Policy Manager for LDAP Authentication Source Configuration and SQL Authentication Source Configuration.
LDAP Authentication Source Configuration
Policy Manager can perform NTLM/MSCHAPv2, PAP Password Authentication Protocol. PAP validates users by password. PAP does not encrypt passwords for transmission and is thus considered insecure./GTC Generic Token Card. GTC is a protocol that can be used as an alternative to MSCHAPv2 protocol. GTC allows authentication to various authentication databases even in cases where MSCHAPv2 is not supported by the database., and certificate-based authentications against any LDAP Lightweight Directory Access Protocol. LDAP is a communication protocol that provides the ability to access and maintain distributed directory information services over a network.-compliant directory (for example, Novell eDirectory, OpenLDAP, and Sun Directory Server). LDAP Lightweight Directory Access Protocol. LDAP is a communication protocol that provides the ability to access and maintain distributed directory information services over a network. and Active Directory Microsoft Active Directory. The directory server that stores information about a variety of things, such as organizations, sites, systems, users, shares, and other network objects or components. It also provides authentication and authorization mechanisms, and a framework within which related services can be deployed.-based server configurations are similar. You can retrieve role-mapping attributes by using filters. To configure Generic LDAP Lightweight Directory Access Protocol. LDAP is a communication protocol that provides the ability to access and maintain distributed directory information services over a network. authentication sources in Policy Manager:
1. Navigate to the Configuration > Authentication > Sources page. The > page opens. The General page labels the authentication source and defines session details.
2. Click . The page opens.
Figure 1 Adding a Generic LDAP Authentication Database
3. Enter the values for these parameters as described in Table 1.
Table 1: General Page Parameters for Generic LDAP Database
|
Parameter |
Action/Description |
|---|---|
|
Name |
Enter the name of the LDAP Lightweight Directory Access Protocol. LDAP is a communication protocol that provides the ability to access and maintain distributed directory information services over a network. authentication source. |
|
Description |
Provide the additional information that helps to identify the LDAP Lightweight Directory Access Protocol. LDAP is a communication protocol that provides the ability to access and maintain distributed directory information services over a network. authentication source. |
|
Type |
Select . |
|
Use for Authorization |
When is enabled, Policy Manager can use this authentication source to fetch role-mapping attributes. This option is enabled by default. |
|
Backup Servers Priority |
To add a backup server in the event the main server goes down, click . Aruba recommends setting up one or more backup servers. |
|
Authorization Sources |
Specifies additional sources from which role-mapping attributes may be fetched. 1. Select a previously configured authentication source from the drop-down list. 2. To add authentication source to the list of authorization sources, click . To remove the authentication source from the list, click . If Policy Manager authenticates the user or device from this authentication source, it also fetches role mapping attributes from these additional authorization sources. |
|
Cache Timeout |
Policy Manager caches attributes fetched for an authenticating entity. This parameter controls the duration in number of seconds for which the attributes are cached. The default is seconds (one hour). |
|
Backup Servers Priority |
To add a backup server, click . If the tab appears, you can specify connection details for a backup server. To remove a backup server, select the server name and click . To change the server priority of the backup servers, select or . This is the order in which Policy Manager attempts to connect to the backup servers when the primary server is unreachable. |
3. When satisfied with these settings, click . The page opens.
Figure 2 Primary Page: Generic LDAP Authentication Database
Table 2: Primary Parameters for an LDAP Authentication Source
4. When satisfied with these settings, click . The page is displayed, which shows all the settings you have entered for the LDAP Lightweight Directory Access Protocol. LDAP is a communication protocol that provides the ability to access and maintain distributed directory information services over a network. authentication source.
SQL Authentication Source Configuration
Policy Manager can perform MSCHAPv2 and PAP Password Authentication Protocol. PAP validates users by password. PAP does not encrypt passwords for transmission and is thus considered insecure./GTC Generic Token Card. GTC is a protocol that can be used as an alternative to MSCHAPv2 protocol. GTC allows authentication to various authentication databases even in cases where MSCHAPv2 is not supported by the database. authentication against any Open Database Connectivity (ODBC) compliant SQL database such as Microsoft SQL Server, Oracle, or PostgrSQL.
You can specify a stored procedure to query the relevant tables and retrieve role-mapping attributes by using filters.
You can configure the primary and backup servers, session details, filter query, and role mapping attributes to fetch the generic SQL authentication sources.
Configuring a Generic SQL Authentication Source
To configure a generic SQL authentication source:
1. Navigate to > > . The page opens.
2. Click . The > page opens. The General page labels the authentication source and defines session details.
Figure 3 General Page: Generic SQL Authentication Database
3. Enter the information for each of the required parameters as described in Table 1.
Table 3: General Page Parameters for Generic SQL Database
|
Parameter |
Action/Description |
|---|---|
|
Name
|
Enter the name of the SQL authentication source. |
|
Description |
Provide the additional information that helps to identify the authentication source. |
|
Type |
Select . |
|
Use for Authorization |
Leave the setting enabled. When is enabled, Policy Manager can use this authentication source to fetch role-mapping attributes. This option is enabled by default. |
|
Backup Servers Priority |
To add a backup server in the event the main server goes down, click . Aruba recommends setting up one or more backup servers. |
|
Authorization Sources |
Specify additional sources from which role-mapping attributes can be fetched. Select a previously configured authentication source from the drop-down list. To add authentication source to the list of authorization sources, click . To remove the authentication source from the list, click . If Policy Manager authenticates the user or device from this authentication source, it also fetches role mapping attributes from these additional authorization sources. |
|
Cache Timeout |
Specify the number of seconds for the . Policy Manager caches attributes fetched for an authenticating entity. This parameter controls the duration in number of seconds for which the attributes are cached. |
|
Backup Servers Priority |
To add a backup server, click . If the tab appears, you can specify connection details for a backup server. To remove a backup server, select the server name and click . To change the server priority of the backup servers, select or . This is the order in which Policy Manager attempts to connect to the backup servers when the primary server is unreachable. |
4. When satisfied with these settings, click . The Authentication Sources page opens.
Figure 4 Primary Page: Generic SQL Authentication Source
5. Enter the information for each of the required parameters as described in Table 4.
Table 4: Primary Page Parameters for Generic SQL Database
|
Parameter |
Action/Description |
|---|---|
|
Server Name |
Enter the name or IP address of the Generic SQL server you’re going to use for authentication. |
|
Port |
Optionally, you can specify a port value to override the default port. |
|
Database Name |
Enter the name of the database from which records can be retrieved. |
|
Login Username |
Enter the name of the user used to log into the database. This account must have read access to all the attributes that need to be retrieved by the specified filters. |
|
Password |
Enter the password for the user account entered in the Login Username field. |
|
Timeout |
Enter the duration in seconds that Policy Manager waits before attempting to fail over from the primary to the backup servers (in the order in which they are configured). |
|
ODBC Driver |
Select the ODBC driver to connect to the database. PostgreSQL Oracle 11g MariaDB MSSQL MySQL is no longer supported for ClearPass 6.7.x and later. MySQL has been replaced by Maria-DB Connector (MariaDB). If you connect to a Microsoft SQL server using Integrated Authentication, the login username in the authentication source, formatted as either domain/username or UPN (User Principal Name), the following characters are supported: Backslash ( \ ) At-sign (@) Hyphen Underscore |
|
Password Type |
Specify how the user password is stored in the database: Cleartext : Password is stored as clear, unencrypted text. NT Hash: Password is stored with an NT hash using MD4 Message Digest 4. MD4 is an earlier version of MD5 and is an algorithm used to verify data integrity through the creation of a 128-bit message digest from data input. . LM Hash : Password is stored with a LAN Local Area Network. A LAN is a network of connected devices within a distinct geographic area such as an office or a commercial establishment and share a common communications line or wireless link to a server. Manager Hash using DES Data Encryption Standard. DES is a common standard for data encryption and a form of secret key cryptography, which uses only one key for encryption and decryption.. SHA Secure Hash Algorithm. SHA is a family of cryptographic hash functions. The SHA algorithm includes the SHA, SHA-1, SHA-2 and SHA-3 variants. : Password is stored with a Secure Hash Algorighm (SHA Secure Hash Algorithm. SHA is a family of cryptographic hash functions. The SHA algorithm includes the SHA, SHA-1, SHA-2 and SHA-3 variants. ) hash. SHA256: Password is stored with an SHA Secure Hash Algorithm. SHA is a family of cryptographic hash functions. The SHA algorithm includes the SHA, SHA-1, SHA-2 and SHA-3 variants. -256 hash function. |
6. When satisfied with the page settings, click . The Attributes page appears. The Attributes page defines the SQL database query filters and the attributes to be fetched when using those filters.
Figure 5 Attributes Page: Generic SQL Authentication Source
7. Enter the information for each of the required parameters as described in Table 5.
Table 5: Attributes Page Parameters for Generic SQL Database
|
Parameter |
Action/Description |
|---|---|
|
Filter Name |
Displays the name of the filter. |
|
Attribute Name |
Specifies the name of the SQL database attributes defined for this filter. |
|
Alias Name |
Specifies an alias name for each attribute name selected for the filter. |
|
Enabled As |
Optionally, indicates whether the filter is enabled as a role or an attribute type. This option can also be blank. |
|
Add More Filters |
Click this button to open the Configure Filter page (for details, see the next section, Defining a Filter Query). Use this page to define a filter query and the related attributes to be fetched from the SQL DB store. |
8. When satisfied with the page settings, click . The page appears.
Defining a Filter Query
The page allows you to define a filter query and the related attributes to be fetched from the SQL DB store.
To define a filter query:
1. Navigate to > > . The s page opens.
a. If you're defining a new filter for an existing authentication source, click the name of the authentication source, then select the tab.
b. If you're defining a new filter query for a newly configured authentication source, follow the steps described in the previous section.
2. From the page, click . The page opens.
Figure 6 Configure Filter Page: Generic SQL Authentication Source
3. Enter the information for each of the required parameters as described in Table 6.
Table 6: Configure Filter Page Parameters for Generic SQL Database
|
Parameter |
Action/Description |
|---|---|
|
Filter Name |
Enter the name of the new filter. |
|
Filter Query
|
Specify an SQL query to fetch the attributes from the user or device record in the database. |
|
Name |
Select Click to add to specify the name of the attribute. |
|
Alias Name |
Specify the alias name for the attribute. By default, this is the same value as the attribute name. |
|
Data Type |
Specify the data type for this attribute, such as String, Integer, or Boolean. |
|
Enabled As |
Specify whether this value is to be used directly as a role or an attribute in an Enforcement Policy. This option bypasses having to assign a role in Policy Manager through a Role Mapping Policy. |
4. When satisfied with the page settings, click .