The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter includes the following sections:
Role-Based Access Control (RBAC) is a method of restricting or authorizing system access for users based on user roles and locales. A role defines the privileges of a user in the system and the locale defines the organizations (domains) that a user is allowed access. Because users are not directly assigned privileges, management of individual user privileges is simply a matter of assigning the appropriate roles and locales.
A user is granted write access to desired system resources only if the assigned role grants the access privileges and the assigned locale allows access. For example, a user with the Server Administrator role in the Engineering organization could update server configurations in the Engineering organization but could not update server configurations in the Finance organization unless the locales assigned to the user include the Finance organization.
User accounts are used to access the system. Up to 128 user accounts can be configured in each Cisco UCS Central domain. Each user account must have a unique username and password.
A user account can be set with a SSH public key. The public key can be set in either of the two formats: OpenSSH and SECSH.
Cisco UCS Central has an admin account. The admin account is a default user account and cannot be modified or deleted. This account is the system administrator or superuser account and has full privileges. There is no default password assigned to the admin account; you must choose the password during the initial system setup.
The admin account is always active and does not expire. You cannot configure the admin account as inactive.
The local admin user is able to login for fail over, even when authentication is set to remote.
A locally authenticated user account is authenticated through the Cisco UCS Central user database, and can be enabled or disabled by anyone with admin or aaa privileges. Once a local user account is disabled, the user cannot log in. Configuration details for disabled local user accounts are not deleted by the database. If you re-enable a disabled local user account, the account becomes active again with the existing configuration, including username and password.
A remotely authenticated user account is any Cisco UCS Central user account that is authenticated through LDAP. Cisco UCS domainssupport LDAP, RADIUS and TACACS+.
If a user maintains a local user account and a remote user account simultaneously, the roles defined in the local user account override those maintained in the remote user account.
User accounts can be configured to expire at a predefined time. When the expiration time is reached, the user account is disabled.
By default, user accounts do not expire.
Note |
After you configure a user account with an expiration date, you cannot reconfigure the account to not expire. You can, however, configure the account with the latest expiration date available. |
The username is also used as the login ID for Cisco UCS Central. When you assign login IDs to Cisco UCS user accounts, consider the following guidelines and restrictions:
The following words cannot be used when creating a local user account in Cisco UCS and Cisco UCS Central.
A password is required for each locally authenticated user account. A user with admin, aaa, or domain-group-management privileges can configure Cisco UCS Central to perform a password strength check on user passwords. If the password strength check is enabled, each user must have a strong password.
Cisco recommends that each user have a strong password. If you enable the password strength check for locally authenticated users, Cisco UCS Central rejects any password that does not meet the following requirements:
Cisco UCS Central does not support managing a number of concurrent web sessions at this time. We do support 32 concurrent web sessions for Cisco UCS Central users and a total of 256 concurrent sessions for all users.
Configuring User Roles
User roles contain one or more privileges that define the operations that are allowed for a user. One or more roles can be assigned to each user. Users with multiple roles have the combined privileges of all assigned roles. For example, if Role1 has storage-related privileges, and Role2 has server-related privileges, users with Role1 and Role2 have both storage-related and server-related privileges.
A Cisco UCS domain can contain up to 48 user roles, including the default user roles. Each domain group in Cisco UCS Central can contain 48 user roles, including the user roles that are inherited from the parent domain group. When user roles are pushed to Cisco UCS Manager from Cisco UCS Central, only the first 48 roles will be active. Any user roles after the first 48 will be inactive with faults raised.
All roles include read access to all configuration settings in the Cisco UCS domain. Users with read-only roles cannot modify the system state.
Roles can be created, modified to add new or remove existing privileges, or deleted. When a role is modified, the new privileges are applied to all users that have that role. Privilege assignment is not restricted to the privileges defined for the default roles. That is, you can use a custom set of privileges to create a unique role. For example, the default Server Administrator and Storage Administrator roles have a different set of privileges, but a new Server and Storage Administrator role can be created that combines the privileges of both roles.
If a role is deleted after it has been assigned to users, it is also deleted from those user accounts.
User profiles on AAA servers (RADIUS or TACACS+) should be modified to add the roles corresponding to the privileges granted to that user. The attribute is used to store the role information. The AAA servers return this attribute with the request and parse it to get the roles. LDAP servers return the roles in the user profile attributes.
The system contains the following default user roles:
Read-and-write access to users, roles, and AAA configuration. Read access to the rest of the system.
Complete read-and-write access to the entire system. The default admin account is assigned this role by default and it cannot be changed.
Read-and-write access to power management operations through the power-mgmt privilege. Read access to the rest of the system.
Read-and-write access to fabric interconnect infrastructure and network security operations. Read access to the rest of the system.
Read-and-write access to systems logs, including the syslog servers, and faults. Read access to the rest of the system.
Read-only access to system configuration with no privileges to modify the system state.
Read and write access to most aspects of service profiles. However the user cannot create, modify or delete vNICs or vHBAs.
Read-and-write access to physical server related operations. Read access to the rest of the system.
Read-and-write access to logical server related operations. Read access to the rest of the system.
Read-and-write access to server security related operations. Read access to the rest of the system.
Read-and-write access to storage operations. Read access to the rest of the system.
The following words cannot be used when creating custom roles in Cisco UCS.
Privileges give users assigned to user roles access to specific system resources and permission to perform specific tasks. The following table lists each privilege and the user role given that privilege by default.
Privilege |
Description |
Default Role Assignment |
---|---|---|
aaa |
System security and AAA |
AAA Administrator |
admin |
System administration |
Administrator |
domain-group-management |
Domain Group Management |
Domain Group Administrator |
ext-lan-config |
External LAN configuration |
Network Administrator |
ext-lan-policy |
External LAN policy |
Network Administrator |
ext-lan-qos |
External LAN QoS |
Network Administrator |
ext-lan-security |
External LAN security |
Network Administrator |
ext-san-config |
External SAN configuration |
Storage Administrator |
ext-san-policy |
External SAN policy |
Storage Administrator |
ext-san-qos |
External SAN QoS |
Storage Administrator |
ext-san-security |
External SAN security |
Storage Administrator |
fault |
Alarms and alarm policies |
Operations |
operations |
Logs and Smart Call Home |
Operations |
org-management |
Organization management |
Operations |
pod-config |
Pod configuration |
Network Administrator |
pod-policy |
Pod policy |
Network Administrator |
pod-qos |
Pod QoS |
Network Administrator |
pod-security |
Pod security |
Network Administrator |
power-mgmt |
Read-and-write access to power management operations |
Facility Manager |
read-only |
Read-only access Read-only cannot be selected as a privilege; it is assigned to every user role. |
Read-Only |
server-equipment |
Server hardware management |
Server Equipment Administrator |
server-maintenance |
Server maintenance |
Server Equipment Administrator |
server-policy |
Server policy |
Server Equipment Administrator |
server-security |
Server security |
Server Security Administrator |
service-profile-compute |
Service profile compute |
Server Compute Administrator |
service-profile-config |
Service profile configuration |
Server Profile Administrator |
service-profile-config-policy |
Service profile configuration policy |
Server Profile Administrator |
service-profile-ext-access |
Service profile end point access |
Server Profile Administrator |
service-profile-network |
Service profile network |
Network Administrator |
service-profile-network-policy |
Service profile network policy |
Network Administrator |
service-profile-qos |
Service profile QoS |
Network Administrator |
service-profile-qos-policy |
Service profile QoS policy |
Network Administrator |
service-profile-security |
Service profile security |
Server Security Administrator |
service-profile-security-policy |
Service profile security policy |
Server Security Administrator |
service-profile-server |
Service profile server management |
Server Profile Administrator |
service-profile-server-oper |
Service profile consumer |
Server Profile Administrator |
service-profile-server-policy |
Service profile pool policy |
Server Security Administrator |
service-profile-storage |
Service profile storage |
Storage Administrator |
service-profile-storage-policy |
Service profile storage policy |
Storage Administrator |
Configuring Locally Authenticated User Accounts
At a minimum, we recommend that you create the following users:
Perform the following tasks, if the system includes any of the following:
Step 1 | On the menu bar, click Administration. |
Step 2 | In the Navigation pane, click the Access Control tab. |
Step 3 | On the Access Control tab, expand Locally Authenticated Users. |
Step 4 | Right-click the User you want to delete, and choose Delete. |
Step 5 | In the Confirm dialog box, click Yes. |
Changes in user roles and privileges do not take effect until the next time the user logs in. If a user is logged in when you assign a new role to or remove an existing role from a user account, the active session continues with the previous roles and privileges.
Step 1 | On the menu bar, click Administration. |
Step 2 | In the Navigation pane, click the Access Control tab. |
Step 3 | On the Access Control tab, expand Locally Authenticated Users. |
Step 4 | Click the user account that you want to modify. |
Step 5 | In the Work pane, click the General tab. |
Step 6 | In the Work pane, click the Roles/Locales tab. |
Step 7 | In the Assigned Role(s) area, assign and remove roles. |
Step 8 | Click Save. |
You must be a user with admin, aaa, or domain-group-management privileges to enable the password strength check. If the password strength check is enabled, Cisco UCS Central does not permit a user to choose a password that does not meet the guidelines for a strong password.
Step 1 | On the menu bar, click Administration. |
Step 2 | In the Navigation pane, click the Access Control tab. |
Step 3 | On the Access Control tab, click Locally Authenticated Users. |
Step 4 | In the Work pane, check the Password Strength Check check box in the Properties area. |
Step 5 | Click Save. |
You must have admin, aaa, or domain-group-management privileges to change the password profile properties.
Step 1 | On the menu bar, click Administration. |
Step 2 | In the Navigation pane, click the Access Control tab. |
Step 3 | On the Access Control tab, click Locally Authenticated Users. |
Step 4 |
In the Password Profile area, enter 0 for the number of unique passwords that a locally authenticated user must create before that user can reuse a previously used password in the History Count field. Setting the History Count field to 0 (the default setting) disables the history count and allows users to reuse previously used passwords at any time. |
Step 5 | Click Save. |
You must be a user with admin, aaa, or domain-group-management privileges to enable or disable a local user account.
Create a local user account.
Step 1 | On the menu bar, click Administration. |
Step 2 | In the Navigation pane, click the Access Control tab. |
Step 3 | On the Access Control tab, expand Locally Authenticated Users. |
Step 4 | Click the user account that you want to modify. |
Step 5 | In the Work pane, click the General tab. |
Step 6 | In the Account Status field, click the active radio button. |
Step 7 | Click Save. |
You must be a user with admin, aaa, or domain-group-management privileges to enable or disable a local user account.
Note |
If you change the password on a disabled account through the Cisco UCS Central GUI, the user cannot use this changed password after you enable the account and make it active. The user must enter the required password again after the account is enabled and made active. |
Step 1 | On the menu bar, click Administration. |
Step 2 | In the Navigation pane, click the Access Control tab. |
Step 3 | On the Access Control tab, expand Locally Authenticated Users. |
Step 4 | Click the user account that you want to modify. |
Step 5 | In the Work pane, click the General tab. |
Step 6 |
In the Account Status field, click the inactive radio button. The admin user account is always set to active. It cannot be modified. |
Step 7 | Click Save. |
Configuring User Locales
A user can be assigned one or more locales. Each locale defines one or more organizations (domains) the user is allowed access, and access would be limited to the organizations specified in the locale. One exception to this rule is a locale without any organizations, which gives unrestricted access to system resources in all organizations.
A Cisco UCS domain can contain up to 48 user locales. Each domain group in Cisco UCS Central can contain 48 user locales, including the user locales that are inherited from the parent domain group. When user locales are pushed to Cisco UCS Manager from Cisco UCS Central, only the first 48 locales will be active. Any user locales after the first 48 will be inactive with faults raised.
Users with admin, aaa, or domain-group-management privileges can assign organizations to the locale of other users.
Note |
You cannot assign a locale to users with the admin privilege. |
You can hierarchically manage organizations. A user that is assigned at a top level organization has automatic access to all organizations under it. For example, an Engineering organization can contain a Software Engineering organization and a Hardware Engineering organization. A locale containing only the Software Engineering organization has access to system resources only within that organization; however, a locale that contains the Engineering organization has access to the resources for both the Software Engineering and Hardware Engineering organizations.
One or more organizations must exist before you create a locale.
Step 1 | On the menu bar, click Operations Management. |
Step 2 | In the Navigation pane select a domain group for the locale. |
Step 3 | Under the Domain Groups node, do one of the following: |
Step 4 | In the Work pane navigate to Locales. |
Step 5 |
Click Create Locales. You can also right-click Locales to access that option. |
Step 6 |
In the Create Locale dialog box enter requested information.
|
Step 7 | Click Filter. |
Step 8 | In the Table Filter dialog box enter requested information. |
Step 9 | Click OK. |
Step 10 | Click Assign Organization. |
Step 11 |
In the Assign Organizations dialog box assign the organization to the locale.
|
Step 12 | Click OK to assign organization. |
Step 13 | Click OK to create locale. |
Step 1 | On the menu bar, click Operations Management. |
Step 2 | In the Navigation pane select a domain group for the locale. |
Step 3 | Under the Domain Groups node, do one of the following: |
Step 4 | In the Work pane display all locales. |
Step 5 | Click the locale which you want to delete. |
Step 6 |
Click Delete. You can also right-click a Locale you want to delete to access that option. |
Step 7 | In the Confirm dialog box, click Yes. |
Step 1 | On the menu bar, click Operations Management. |
Step 2 | In the Navigation pane select a domain group for the locale. |
Step 3 | Under the Domain Groups node, do one of the following: |
Step 4 | In the Work pane select a locale. |
Step 5 | Click the locale to which you want to add an organization. |
Step 6 |
Click Assign Organization. You can also right-click the Locale to access that option. |
Step 7 | In the Assign Organizations dialog box enter the Organization. |
Step 8 | Click OK. |
Step 1 | On the menu bar, click Operations Management. |
Step 2 | In the Navigation pane select a domain group for the locale. |
Step 3 | Under the Domain Groups node, do one of the following: |
Step 4 | In the Work pane display all locales. |
Step 5 | Click the locale with an assigned organization you want to delete. |
Step 6 | Click Properties. |
Step 7 | In the Work pane, click the Organization you want to delete. |
Step 8 |
Click Delete. You can also right-click an Organization you want to delete to access that option. |
Step 9 | In the Confirm dialog box, click Yes. |
Note |
Do not assign locales to users with an admin role. |
Step 1 | On the menu bar, click Administration. |
Step 2 | In the Navigation pane, click the Access Control tab. |
Step 3 | On the Access Control tab, expand Locally Authenticated Users. |
Step 4 | Click the user account that you want to modify. |
Step 5 | In the Work pane, click the General tab. |
Step 6 | In the Work pane, click the Roles/Locales tab. |
Step 7 | In the Assigned Locale(s) area, assign and remove locales. |
Step 8 | Click Save. |
Configuring User Domain Groups
Step 1 | On the menu bar, click Operations Management. |
Step 2 | In the Navigation pane, click Domain Groups and do one of the following choices: |
Step 3 |
In the Create Domain Group dialog box enter requested information.
|
Step 4 | Click OK to create domain group. |
Step 1 | On the menu bar, click Operations Management. | ||
Step 2 | In the Navigation pane, click Domain Groups. | ||
Step 3 | In the Domain Groups pane under the Name column, click the Domain Group you want to delete. | ||
Step 4 |
Click Delete.
|
||
Step 5 | In the Confirm dialog box, click Yes. |
Configuring User Organizations
A user can create one or more organizations. Each organization defines sub-organizations, faults, events, UUID suffix pools and blocks of UUIDs.
Cisco UCS organizations are hierarchically managed by users. A user that is assigned at the root level organization has automatic access to all organizations and domain groups under it.
Step 1 | On the menu bar, click Servers. |
Step 2 | In the Navigation pane create an organization. |
Step 3 |
In the Create Organization dialog box enter requested information.
|
Step 4 | Click OK to create an organization. |
Step 1 | On the menu bar, click Servers. |
Step 2 | In the Navigation pane select an organization. |
Step 3 |
Click Delete. You can also right-click the Organization you want to delete to access that option. |
Step 4 | In the Confirm dialog box, click Yes. |
Step 1 | On the menu bar, click Servers. |
Step 2 | In the Navigation pane create a sub-organization. |
Step 3 | In the Sub-Organizations pane, click applicable assigned organization name. |
Step 4 | In the Work pane, click Create Organization. |
Step 5 |
In the Create Organization dialog box enter requested information.
|
Step 6 | Click OK to create a sub-organization. |
Step 1 | On the menu bar, click Servers. |
Step 2 |
In the Navigation pane select an organization.
|
Step 3 |
Click Delete. You can also expand the Organizations until reaching the target you want to delete, and right-click an Organization to access that option. |
Step 4 | In the Confirm dialog box, click Yes. |
Configuring Passwords
The password profile contains the password history and password change interval properties for all locally authenticated users of Cisco UCS Central. You cannot specify a different password profile for each locally authenticated user.
Note |
You must have admin, aaa, or domain-group-management privileges to change the password profile properties. Except for password history, these properties do not apply to users with these administrative privileges. |
The password history count allows you to prevent locally authenticated users from reusing the same password over and over again. When this property is configured, Cisco UCS Central stores passwords that were previously used by locally authenticated users up to a maximum of 15 passwords. The passwords are stored in reverse chronological order with the most recent password first to ensure that the only the oldest password can be reused when the history count threshold is reached.
A user must create and use the number of passwords configured in the password history count before being able to reuse one. For example, if you set the password history count to 8, a locally authenticated user cannot reuse the first password until after the ninth password has expired.
By default, the password history is set to 0. This value disables the history count and allows users to reuse previously passwords at any time.
If necessary, you can clear the password history count for a locally authenticated user and enable reuse of previous passwords.
The password change interval enables you to restrict the number of password changes a locally authenticated user can make within a given number of hours. The following table describes the two configuration options for the password change interval.
Interval Configuration | Description | Example |
---|---|---|
No password change allowed |
This option does not allow passwords for locally authenticated users to be changed within a specified number of hours after a password change. You can specify a no change interval between 1 and 745 hours. By default, the no change interval is 24 hours. |
For example, to prevent passwords from being changed within 48 hours after a locally authenticated user changes his or her password, set the following: |
Password changes allowed within change interval |
This option specifies the maximum number of times that passwords for locally authenticated users can be changed within a pre-defined interval. You can specify a change interval between 1 and 745 hours and a maximum number of password changes between 0 and 10. By default, a locally authenticated user is permitted a maximum of 2 password changes within a 48 hour interval. |
For example, to allow to be changed a maximum of once within 24 hours after a locally authenticated user changes his or her password, set the following: |
You must have admin or aaa privileges to change the password profile properties. Except for password history, these properties do not apply to users with admin or aaa privileges.
Step 1 | On the menu bar, click Administration. |
Step 2 | In the Navigation pane, click the Access Control tab. |
Step 3 | On the Access Control tab, click Locally Authenticated Users. |
Step 4 |
In the Password Profile area complete all fields.
|
Step 5 | Click Save. |
You must have admin or aaa privileges to change the password profile properties. Except for password history, these properties do not apply to users with admin or aaa privileges.
Step 1 | On the menu bar, click Administration. |
Step 2 | In the Navigation pane, click the Access Control tab. |
Step 3 | On the Access Control tab, click Locally Authenticated Users. |
Step 4 |
In the Password Profile area complete all fields.
|
Step 5 | Click Save. |
You must have admin or aaa privileges to change the password profile properties.
Step 1 | On the menu bar, click Administration. |
Step 2 | In the Navigation pane, click the Access Control tab. |
Step 3 | On the Access Control tab, click Locally Authenticated Users. |
Step 4 |
In the Password Profile area, enter the number of unique passwords that a locally authenticated user must create before that user can reuse a previously used password in the History Count field. This value can be anywhere from 0 to 15. By default, the History Count field is set to 0, which disables the history count and allows users to reuse previously used passwords at any time. |
Step 5 | Click Save. |
You can monitor Cisco UCS Central sessions for both locally authenticated users and remotely authenticated users, whether they logged in through the CLI or the GUI.
Step 1 | On the menu bar, click Administration. | ||||||||||||||
Step 2 | On the Access Control tab, click Locally Authenticated Users or Remotely Authenticated Users. | ||||||||||||||
Step 3 | In the Navigation pane, user sessions are monitored under Locally Authenticated Users for all users or each user. | ||||||||||||||
Step 4 |
In the Work pane, click the Sessions tab. The tab displays the following details of user sessions:
|