User Management. Cisco FXOS Firepower Chassis Manager
广告
广告
C H A P T E R
4
User Management
•
•
Guidelines for Usernames, page 20
•
Guidelines for Passwords, page 21
•
Guidelines for Remote Authentication, page 21
•
•
Password Profile for Locally Authenticated Users, page 24
•
Configuring User Settings, page 25
•
Set the Maximum Number of Login Attempts, page 27
•
Configure Minimum Password Length Check, page 28
•
Creating a Local User Account, page 29
•
Deleting a Local User Account, page 30
•
Activating or Deactivating a Local User Account, page 30
User Accounts
User accounts are used to access the system. You can configure up to 48 local user accounts. Each user account must have a unique username and password.
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.
Locally Authenticated User Accounts
A locally authenticated user account is authenticated directly through the chassis 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.
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
19
User Management
Guidelines for Usernames
Configuration details for disabled local user accounts are not deleted by the database. If you reenable a disabled local user account, the account becomes active again with the existing configuration, including username and password.
Remotely Authenticated User Accounts
A remotely authenticated user account is any user account that is authenticated through LDAP, RADIUS, or
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.
See the following topics for more information on guidelines for remote authentication, and how to configure and delete remote authentication providers:
•
Guidelines for Remote Authentication, on page 21
•
Configuring LDAP Providers, on page 101
•
Configuring RADIUS Providers, on page 104
•
Configuring TACACS+ Providers, on page 106
Expiration of User Accounts
You can configure user accounts to expire at a predefined time. When the expiration time is reached, the user account is disabled.
By default, user accounts do not expire.
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.
Guidelines for Usernames
The username is also used as the login ID for Firepower Chassis Manager and the FXOS CLI. When you assign login IDs to user accounts, consider the following guidelines and restrictions:
• The login ID can contain between 1 and 32 characters, including the following:
◦ Any alphabetic character
◦ Any digit
◦ _ (underscore)
◦ - (dash)
◦ . (dot)
• The login ID must be unique.
• The login ID must start with an alphabetic character. It cannot start with a number or a special character, such as an underscore.
• The login ID is case-sensitive.
• You cannot create an all-numeric login ID.
20
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
User Management
Guidelines for Passwords
• After you create a user account, you cannot change the login ID. You must delete the user account and create a new one.
Guidelines for Passwords
A password is required for each locally authenticated user account. A user with admin or AAA privileges can configure the system to perform a password strength check on user passwords. If the password strength check is enabled, each user must have a strong password.
We recommend that each user have a strong password. If you enable the password strength check for locally authenticated users, the Firepower eXtensible Operating System rejects any password that does not meet the following requirements:
• Must contain a minimum of 8 characters and a maximum of 80 characters.
Note
You can optionally configure a minimum password length of 15 characters on the system, to comply with Common Criteria requirements. For more information, see
Minimum Password Length Check, on page 28
.
• Must include at least one uppercase alphabetic character.
• Must include at least one lowercase alphabetic character.
• Must include at least one non-alphanumeric (special) character.
• Must not contain a character that is repeated more than 3 times consecutively, such as aaabbb.
• Must not contain three consecutive numbers or letters in any order, such as passwordABC or password321.
• Must not be identical to the username or the reverse of the username.
• Must pass a password dictionary check. For example, the password must not be based on a standard dictionary word.
• Must not contain the following symbols: $ (dollar sign), ? (question mark), and = (equals sign).
• Must not be blank for local user and admin accounts.
Guidelines for Remote Authentication
If a system is configured for one of the supported remote authentication services, you must create a provider for that service to ensure that the FXOS chassis can communicate with the system. The following guidelines impact user authorization:
User Accounts in Remote Authentication Services
User accounts can exist locally in the FXOS chassis or in the remote authentication server.
You can view the temporary sessions for users who log in through remote authentication services from the FXOS Chassis Manager GUI and from the FXOS CLI.
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
21
User Management
Guidelines for Remote Authentication
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 the FXOS chassis and that the names of those roles match the names used in FXOS. Based on the role policy, a user might not be allowed to log in, or is granted only read-only privileges.
User Attributes in Remote Authentication Providers
For RADIUS and TACAS+ configurations, you must configure a user attribute for the FXOS chassis in each remote authentication provider through which users log in to Firepower Chassis Manager and the FXOS CLI.
This user attribute holds the roles and locales assigned to each user.
When a user logs in, FXOS does the following:
1
Queries the remote authentication service.
2
Validates the user.
3
If the user is validated, checks the roles and locales assigned to that user.
The following table contains a comparison of the user attribute requirements for the remote authentication providers supported by FXOS:
Authenication Provider
LDAP
Custom Attribute
Optional
Schema Extension Attribute ID Requirements
You can choose to do one of the following:
The Cisco LDAP implementation requires a unicode type attribute.
• Do not extend the
LDAP schema and configure an existing, unused attribute that meets the requirements.
If you choose to create the
CiscoAVPair custom attribute, use the following attribute ID:
1.3.6.1.4.1.9.287247.1
A sample OID is provided in the following section.
• Extend the LDAP schema and create a custom attribute with a unique name, such as
CiscoAVPair.
22
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
User Management
Guidelines for Remote Authentication
Authenication Provider
RADIUS
TACAS
Custom Attribute
Optional
Required
Schema Extension Attribute ID Requirements
You can choose to do one of the following:
•
• Do not extend the
RADIUS schema and use an existing, unused attribute that meets the requirements.
Extend the
RADIUS schema and create a custom attribute with a unique name, such as cisco-avpair.
The vendor ID for the
Cisco RADIUS implementation is 009 and the vendor ID for the attribute is 001.
The following syntax example shows how to specify multiples user roles and locales if you choose to create the cisco-avpair attribute: shell:roles="admin,aaa" shell:locales="L1,abc"
.
Use a comma "," as the delimiter to separate multiple values.
You must extend the schema and create a custom attribute with the name cisco-av-pair.
The cisco-av-pair name is the string that provides the attribute ID for the
TACACS+ provider.
The following syntax example shows how to specify multiples user roles and locales when you create the cisco-av-pair attribute: cisco-av-pair=shell:roles="admin aaa" shell:locales*"L1 abc"
. Using an asterisk
(*) in the cisco-av-pair attribute syntax flags the locale as optional, preventing authentication failures for other Cisco devices that use the same authorization profile. Use a space as the delimiter to separate multiple values.
Sample OID for LDAP User Attribute
The following is a sample OID for a custom CiscoAVPair attribute:
CN=CiscoAVPair,CN=Schema,
CN=Configuration,CN=X
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
23
User Management
User Roles
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=X
User Roles
The system contains the following user roles:
Administrator
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-Only
Read-only access to system configuration with no privileges to modify the system state.
Operations
Read-and-write access to NTP configuration, Smart Call Home configuration for Smart Licensing, and system logs, including syslog servers and faults. Read access to the rest of the system.
AAA Administrator
Read-and-write access to users, roles, and AAA configuration. Read access to the rest of the system.
Password Profile for Locally Authenticated Users
The password profile contains the password history and password change interval properties for all locally authenticated users. You cannot specify a different password profile for each locally authenticated user.
Password History Count
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, the Firepower chassis 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.
24
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
User Management
Configuring User Settings
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.
Password Change Interval
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
No password change allowed
Description
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.
Example
For example, to prevent passwords from being changed within 48 hours after a locally authenticated user changes his or her password, set the following:
• Change during interval to disable
• No change interval to 48
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 a password to be changed a maximum of once within 24 hours after a locally authenticated user changes his or her password, set the following:
•
•
• Change during interval to enable
Change count to 1
Change interval to 24
Configuring User Settings
Procedure
Step 1
Choose
System
>
User Management
.
Step 2
Click the
Settings
tab.
Step 3
Complete the following fields with the required information:
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
25
User Management
Configuring User Settings
Name
Default Authentication
field
Description
The default method by which a user is authenticated during remote login. This can be one of the following:
•
Local
— The user account must be defined locally on the Firepower chassis.
•
Radius
—
The user account must be defined on the RADIUS server specified for the Firepower chassis.
•
TACACS
— The user account must be defined on the TACACS+ server specified for the Firepower chassis.
•
LDAP
— The user account must be defined on the LDAP/MS-AD server specified for the Firepower chassis.
•
None
—
If the user account is local to the Firepower chassis, no password is required when the user logs in remotely.
Remote User Settings
Remote User Role Policy Controls what happens when a user attempts to log in and the remote authentication provider does not supply a user role with the authentication information:
•
Assign Default Role
— The user is allowed to log in with a read-only user role.
•
No-Login
— The user is not allowed to log in to the system, even if the username and password are correct.
Local User Settings
Password Strength Check
check box
If checked, all local user passwords must conform to the guidelines for a strong password (see
Guidelines for Passwords, on page 21
).
History Count
field The number of unique passwords a user must create before the user can reuse a previously used password. The history count is in reverse chronological order with the most recent password first to ensure that only the oldest password can be reused when the history count threshold is reached.
This value can be anywhere from 0 to 15.
You can set the
History Count
field to 0 to disable the history count and allow users to reuse previously used passwords at any time.
26
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
User Management
Set the Maximum Number of Login Attempts
Name
Change During Interval
field
Description
Controls when a locally authenticated user can change his or her password. This can be:
•
Enable
— Locally authenticated users can change their passwords based on the settings for Change Interval and Change Count.
•
Disable
—
Locally authenticated users cannot change their passwords for the period of time specified for No Change Interval.
Change Interval
field
Change Count
field
No Change Interval
field
The number of hours over which the number of password changes specified in the
Change Count
field are enforced.
This value can be anywhere from 1 to 745 hours.
For example, if this field is set to 48 and the
Change Count
field is set to 2, a locally authenticated user can make no more than 2 password changes within a 48 hour period.
The maximum number of times a locally authenticated user can change his or her password during the Change Interval.
This value can be anywhere from 0 to 10.
The minimum number of hours that a locally authenticated user must wait before changing a newly created password.
This value can be anywhere from 1 to 745 hours.
This interval is ignored if the
Change During Interval
property is not set to
Disable
.
Step 4
Click
Save
.
Set the Maximum Number of Login Attempts
You can configure the maximum number of failed login attempts allowed before a user is locked out of the
FXOS chassis for a specified amount of time. If a user exceeds the set maximum number of login attempts, the user is locked out of the system. No notification appears indicating that the user is locked out. In this event, the user must wait the specified amount of time before attempting to log in.
Perform these steps to configure the maximum number of login attempts.
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
27
User Management
Configure Minimum Password Length Check
Note
• All types of user accounts (including admin) are locked out of the system after exceeding the maximum number of login attempts.
• The default maximum number of unsuccessful login attempts is 3. The default amount of time the user is locked out of the system after exceeding the maximum number of login attemps is 30 minutes
(3600 seconds).
This option is one of a number offered for achieving Common Criteria certification compliance on your system. For more information, see
Security Certifications Compliance, on page 39
.
Procedure
Step 1
From the FXOS CLI, enter security mode:
scope system scope security
Step 2
Set the maximum number of unsuccessful login attempts.
set max-login-attempts
max_login
The
max_login
value is any integer from 0-10.
Step 3
Specify the amount of time (in seconds) the user should remain locked out of the system after reaching the maximum number of login attempts:
set user-account-unlock-time
unlock_time
Step 4
Commit the configuration:
commit-buffer
Configure Minimum Password Length Check
If you enable minimum password length check, you must create passwords with the specified minimum number of characters. For example, if the
min_length
option is set to 15, you must create passwords using 15 characters or more. This option is one of a number that allow for Common Criteria certification compliance on your system. For more information, see
Security Certifications Compliance, on page 39
.
Perform these steps to configure the minimum password length check.
Procedure
Step 1
From the FXOS CLI, enter security mode:
Step 2 scope system scope security
28
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
User Management
Creating a Local User Account
Step 3
Enter password profile security mode:
scope password-profile
Step 4
Specify the minimum password length:
set min-password-length min_length
Step 5
Commit the configuration:
commit-buffer
Creating a Local User Account
Procedure
Step 1
Choose
System
>
User Management
.
Step 2
Click the
Local Users
tab.
Step 3
Click
Add User
to open the
Add User
dialog box.
Step 4
Complete the following fields with the required information about the user:
Name Description
User Name
field The account name that is used when logging into this account. This name must be unique and meet the guidelines and restrictions for user account names (see
Guidelines for Usernames, on page 20
).
After you save the user, the login ID cannot be changed. You must delete the user account and create a new one.
First Name
field The first name of the user. This field can contain up to 32 characters.
Last Name
field field
Phone Number
field
The last name of the user. This field can contain up to 32 characters.
The email address for the user.
The telephone number for the user.
Password
field
Confirm Password
Account Status
field field
The password associated with this account. If password strength check is enabled, a user's password must be strong and the Firepower eXtensible Operating System rejects any password that does not meet the strength check requirements (see
Guidelines for Passwords, on page
21 ).
The password a second time for confirmation purposes.
If the status is set to
Active
, a user can log into Firepower Chassis
Manager and the FXOS CLI with this login ID and password.
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
29
User Management
Deleting a Local User Account
Name
User Role
list
Account Expires
check box
Expiry Date
field
Description
The role that represents the privileges you want to assign to the user account (see
).
All users are assigned the Read-Only role by default and this role cannot be deselected. To assign multiple roles, hold down Ctrl and click the desired roles.
Note
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.
If checked, this account expires and cannot be used after the date specified in the
Expiration Date
field.
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 date on which the account expires. The date should be in the format yyyy-mm-dd.
Click the calendar icon at the end of this field to view a calendar that you can use to select the expiration date.
Step 5
Click
Add
.
Deleting a Local User Account
Procedure
Step 1
Choose
System
>
User Management
.
Step 2
Click the
Local Users
tab.
Step 3
In the row for the user account that you want to delete, click
Delete
.
Step 4
In the
Confirm
dialog box, click
Yes
.
Activating or Deactivating a Local User Account
You must be a user with admin or AAA privileges to activate or deactivate a local user account.
30
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
User Management
Activating or Deactivating a Local User Account
Procedure
Step 1
Choose
System
>
User Management
.
Step 2
Click the
Local Users
tab.
Step 3
In the row for the user account that you want to activate or deactivate, click
Edit (pencil icon)
.
Step 4
In the
Edit User
dialog box, do one of the following:
• To activate a user account, click the
Active
radio button in the
Account Status
field.
• To deactivate a user account, click the
Inactive
radio button in the
Account Status
field.
The admin user account is always set to active. It cannot be modified.
Step 5
Click
Save
.
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
31
Activating or Deactivating a Local User Account
User Management
32
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
文档公共链接
广告