Feedback
Contents
Configuring Primary Authentication
This chapter includes the following sections:
- Primary Authentication
- Remote Authentication Providers
- Creating an LDAP Provider
- Creating a RADIUS Provider
- Creating a TACACS+ Provider
- Selecting the Console Authentication Service
- Selecting the Default Authentication Service
Primary Authentication
Cisco UCS supports two methods to authenticate user logins:
Note
You can only use one authentication method. For example, if you select LDAP as your authentication provider, you cannot use RADIUS or TACACS+ for authentication. However, if the user account in the remote authentication provider does not have at least one Cisco UCS role, Cisco UCS Manager checks the local database to determine whether an account with the same name exists in the local database.
Remote Authentication Providers
If a system is configured for one of the supported remote authentication services, you must create a provider for that service to ensure that Cisco UCS Manager can communicate with it. In addition, you need to be aware of the following guidelines that impact user authorization:
User Accounts in Remote Authentication Services
You can create user accounts in Cisco UCS Manager or in the remote authentication server.
The temporary sessions for users who log in through remote authentication services can be viewed through Cisco UCS Manager GUI or Cisco UCS Manager CLI.
User Roles in Remote Authentication Services
If you create user accounts in the remote authentication server, you must ensure that the accounts include the roles those users require for working in Cisco UCS Manager and that the names of those roles match the names used in Cisco UCS Manager. If an account does not have the required roles, the user is granted only read-only privileges.
User Attribute for LDAP
If a Cisco UCS instance uses LDAP as the remote authentication provider, you can do one of the following:
Map an existing attribute to the user roles and locale for the Cisco UCS instance.
Create a CiscoAVPair or other unique attribute in the LDAP service and map that attribute to the user roles and locale for the Cisco UCS instance.
You must configure the LDAP provider in Cisco UCS Manager with the attribute that holds the user roles and locales. When a user logs in, Cisco UCS Manager checks for the value of this attribute when it queries the remote authentication service and validates the user.
If you create a CiscoAVPair attribute for the Cisco UCS instance, use the following definition for the OID:
CN=CiscoAVPair,CN=Schema,CN=Configuration,CN=X objectClass: top objectClass: attributeSchema cn: CiscoAVPair distinguishedName: CN=CiscoAVPair,CN=Schema,CN=Configuration,CN=X instanceType: 0x4 uSNCreated: 26318654 attributeID: 1.3.6.1.4.1.9.287247.1 attributeSyntax: 2.5.5.12 isSingleValued: TRUE showInAdvancedViewOnly: TRUE adminDisplayName: CiscoAVPair adminDescription: UCS User Authorization Field oMSyntax: 64 lDAPDisplayName: CiscoAVPair name: CiscoAVPair objectCategory: CN=Attribute-Schema,CN=Schema,CN=Configuration,CN=XRequired User Attribute for RADIUS and TACACS+
If a Cisco UCS instance uses either RADIUS or TACACS+ as the remote authentication provider, you must create a cisco-av-pair attribute in the remote authentication service and map that attribute to the user roles and locale for the Cisco UCS instance. When a user logs in, Cisco UCS Manager checks for the value of this attribute when it queries the remote authentication service and validates the user.
NoteYou cannot use any other attribute in RADIUS or TACAC+ for the Cisco UCS roles. You must create the attribute required for that specific remote authentication service.
Creating a Remote Authentication Provider
Creating an LDAP Provider
Before You BeginProcedurePerform the following configuration in the LDAP server:
Configure users with the attribute that holds the user role and locale information for Cisco UCS Manager. You can use an existing LDAP attribute that is mapped to the Cisco UCS user roles and locales or create a custom attribute, such as the CiscoAVPair attribute, which has an attribute ID of 1.3.6.1.4.1.9.287247.1.
For a cluster configuration, add the management port IP addresses for both fabric interconnects. This configuration ensures that remote users can continue to log in if the first fabric interconnect fails and the system fails over to the second fabric interconnect. All log-in requests are sourced from these IP addresses, not the virtual IP address used by Cisco UCS Manager.
The following example sets the LDAP attribute to CiscoAvPair, the base distinguished name to "DC=nuova-sam-aaa3,DC=qalab,DC=com", the filter to sAMAccountName=$userid, the timeout interval to 5 seconds, creates a server instance named 10.193.169.246, disables SSL, sets the key, sets the authentication port to 389, sets the root distinguished name to "cn=Administrator,cn=Users,DC=nuova-sam-aaa3,DC=qalab,DC=com", and commits the transaction:
UCS-A# scope security UCS-A /security # scope ldap UCS-A /security/ldap # set attribute CiscoAvPair UCS-A /security/ldap* # set basedn "DC=cisco-ucsm-aaa3,DC=qalab,DC=com" UCS-A /security/ldap* # set filter sAMAccountName=$userid UCS-A /security/ldap* # set timeout 5 UCS-A /security/ldap* # create server 10.193.169.246 UCS-A /security/ldap/server* # set ssl no UCS-A /security/ldap/server* # set key Enter the key: Confirm the key: UCS-A /security/ldap/server* # set port 389 UCS-A /security/ldap/server* # set binddn "cn=Administrator,cn=Users,DC=cisco-ucsm-aaa3,DC=qalab,DC=com" UCS-A /security/ldap/server* # commit-buffer UCS-A /security/ldap/server #Creating a RADIUS Provider
ProcedureThe following example sets the RADIUS retries to 4, the timeout interval to 30 seconds, creates a server instance named radiusserv7, sets the authentication port to 5858, sets the key to radiuskey321, and commits the transaction:
UCS-A# scope security UCS-A /security # scope radius UCS-A /security/radius # set retries 4 UCS-A /security/radius* # set timeout 30 UCS-A /security/radius* # create server radiusserv7 UCS-A /security/radius/server* # set authport 5858 UCS-A /security/radius/server* # set key Enter the key: radiuskey321 Confirm the key: radiuskey321 UCS-A /security/radius/server* # commit-buffer UCS-A /security/radius/server #Creating a TACACS+ Provider
ProcedureThe following example sets the TACACS+ timeout interval to 45 seconds, creates a server instance named tacacsserv680, sets the key to tacacskey321, sets the authentication port to 5859, and commits the transaction:
UCS-A# scope security UCS-A /security # scope tacacs UCS-A /security/tacacs # set timeout 45 UCS-A /security/tacacs* # create server tacacsserv680 UCS-A /security/tacacs/server* # set key Enter the key: tacacskey321 Confirm the key: tacacskey321 UCS-A /security/tacacs/server* # set port 5859 UCS-A /security/tacacs/server* # commit-buffer UCS-A /security/tacacs/server #Selecting a Primary Authentication Service
Selecting the Console Authentication Service
