User account and password management

Last published : Sep 24, 2026
NetScaler enables you to manage user accounts and password configuration. Following are some of the activities that you can perform using a system user account or nsroot administrative user account.
  • System user account lockout
  • Lock system user account for management access
  • Unlock a locked system user account for management access
  • Disable management access for system user account
  • Force passwords change for nsroot administrative users
  • Remove sensitive files in a system user account
  • Strong password configuration for system users
  • Enforce password rotation and password history for local accounts

System user account lockout

To prevent brute force security attacks, you can configure the user lockout configuration. The configuration enables a network administrator to prevent a system user to log on to NetScaler. Also, unlock the user account before the lock period expires.
To get the details of the unsuccessful user login attempts across reboots, the persistentLoginAttemptsparameter can be enabled.
At the command prompt, type:
set aaa parameter -maxloginAttempts <value> -failedLoginTimeout <value> -persistentLoginAttempts (ENABLED | DISABLED)
Example:
set aaa parameter -maxloginAttempts 3 -failedLoginTimeout 10 -persistentLoginAttempts ENABLED
Note:
For the aaa.user.login_attempts expression to take effect, you must disable the "Persistent Login Attempts" parameter.
Run the unset aaa parameter -persistentLoginAttempts command to disable (if enabled) the persistent login attempts.
For details about the login attempt functionality, see Support to retrieve current login attempts for a user.
The following show command output displays the configuration status of the authentication, authorization, and auditing parameters:
show aaaparameter

Configured AAA parameters

EnableStaticPageCaching: YES

EnableEnhancedAuthFeedback: NO

DefaultAuthType: LOCAL MaxAAAUsers: Unlimited

AAAD nat ip: None

EnableSessionStickiness : NO

aaaSessionLoglevel: INFORMATIONAL

AAAD Log Level: INFORMATIONAL

...

Persistent Login Attempts: DISABLED

Configure system user account lockout by using the GUI

  1. Navigate to Configuration > Security > AAA-Application Traffic > Authentication Settings > Change authentication AAA Settings.
  2. In the Configure AAA Parameter page, set the following parameters:
    1. Max Login Attempts. The maximum number of logon attempts allowed for the user to try.
    2. Failed Login Timeout. The maximum number of invalid logon attempts by the user.
    3. Persistent Login Attempts. Persistent storage of unsuccessful user login attempts across reboots.
  3. Click OK.
    GUI configuration for system user account lockout
When you set the parameters, the user account gets locked for 10 minutes for three or more invalid login attempts. Also, the user cannot log on even with valid credentials for 10 minutes.
Note
If a locked user tries to log on to NetScaler, an error message, RBA Authentication Failure: maxlogin attempt reached for test. appears.

Lock system user account for management access

NetScaler enables you to lock a system user for 24 hours and deny access to the user.
NetScaler supports the configuration for both system user and external users.
Note
The feature is supported only if you disable the persistentLoginAttempts option in the aaa parameter.
At the command prompt type:
set aaa parameter –persistentLoginAttempts DISABLED
Now, to lock a user account, at the command prompt, type:
lock aaa user test

Lock a system user account by using the GUI

  1. Navigate to Configuration > Security > AAA-Application Traffic > Authentication Settings > Change authentication AAA Settings.
  2. In Configure AAA Parameter, in the Persistent Login Attempts list, select DISABLED.
  3. Navigate to System > User Administration > Users.
  4. Select a user.
  5. In the Select Action list, select Lock.
    Select the lock option
Note
The NetScaler GUI does not provide a way to lock external users. To lock an external user, the ADC administrator must use the CLI.
When a locked system user (locked with lock authentication, authorization, and auditing user command) attempts to log in to NetScaler, an error message, “RBA Authentication Failure: User test is locked down for 24 hours.” appears.
When a user is locked from management access, they can still log in through the console.

Unlock a locked system user account for management access

System users and external users can be locked for 24 hours using the lock authentication, authorization, and auditing user command.
Note
NetScaler allows admins to unlock the locked user and the feature does not require any settings in the “persistentloginAttempts” command.
At the command prompt, type:
unlock aaa user test

Configure system user unlock by using the GUI

  1. Navigate to System > User Administration > Users.
  2. Select a user.
  3. Click Unlock.
    Configure system user unlock
The NetScaler GUI only lists system users created in NetScaler, so there is no option in the GUI to unlock external users. To unlock an external user, the nsroot administrator must use the CLI.

Disable management access for system user account

When external authentication is configured on NetScaler and as an admin, if you prefer to deny access to system users to log on to management access, you must disable the localAuth option in the system parameter.
At the command prompt, type the following:
set system parameter localAuth <ENABLED|DISABLED>
Example:
set system parameter localAuth DISABLED

Disable management access to system user by using the GUI

  1. Navigate to Configuration > System > Settings > Change Global System Settings.
  2. In Command Line Interface (CLI) section, unselect the Local Authentication checkbox.
By disabling the option, local system users cannot log on to ADC management access.
Note
External authentication server must be configured and reachable to disallow local system user authentication in the system parameter. If an external server configured in ADC for management access is unreachable, local system users can log on to NetScaler. The behavior is set up for recovery purpose.

Force passwords change for administrative users

For nsroot secured authentication, NetScaler prompts the user to change the default password to a new one if the forcePasswordChange option is enabled in the system parameter. You can change your nsroot password either from CLI or GUI, on your first login with the default credentials.
At the command prompt, type:
set system parameter -forcePasswordChange ( ENABLED | DISABLED )
SSH session example for NSIP:
ssh nsroot@1.1.1.1
Connecting to 1.1.1.1:22...
Connection established.
To escape to local shell, press Ctrl+Alt+].
###############################################################################
WARNING: Access to this system is for authorized users only #
Disconnect IMMEDIATELY if you are not an authorized user! #

###############################################################################
Please change the default NSROOT password.
Enter new password:
Please re-enter your password:
Done

Remove sensitive files in a system user account

To manage sensitive data such as authorized keys and public keys for a system user account, you must enable the removeSensitiveFiles option. The commands that remove sensitive files when the system parameter is enabled are:
  • rm cluster instance
  • rm cluster node
  • rm high availability node
  • clear config full
  • join cluster
  • add cluster instance
At the command prompt, type:
set system parameter removeSensitiveFiles ( ENABLED | DISABLED )
Example:
set system parameter -removeSensitiveFiles ENABLED

Strong password configuration for system users

For secured authentication, NetScaler prompts system users and administrators to set strong passwords to log on to the console. The password must be long and must be a combination of:
  • One lower case character
  • One upper case character
  • One numeric character
  • One special character
At the command prompt, type:
set system parameter -strongpassword <value> -minpasswordlen <value>
Where,
Strongpassword. After enabling strong password (enable all / enablelocal) all the passwords or sensitive information must have the following:
  • At least 1 lower case character
  • At least 1 upper case character
  • At least 1 numeric character
  • At least 1 special character
Exclude the list in enablelocal is - NS_FIPS, NS_CRL, NS_RSAKEY, NS_PKCS12, NS_PKCS8, NS_LDAP, NS_TACACS, NS_TACACSACTION, NS_RADIUS, NS_RADIUSACTION, NS_ENCRYPTION_PARAMS. So no Strong Password checks are performed on these ObjectType commands for the system user.
Possible values: enableall, enablelocal, disabled Default value: disabled
minpasswordlen. Minimum length of the system user password. When the strong password is enabled by default, the minimum length is 4. User entered value can be greater than or equal to 4. The default minimum value is 1 when the strong password is disabled. The maximum value is 127 in both cases.
Minimum value: 1 Maximum value: 127
Example:
set system parameter -strongpassword enablelocal -minpasswordlen 6

Enforce password rotation and password history for local accounts

NetScaler® includes improved password security features for local user accounts. This feature allows administrators to:
  • Force users to change their passwords regularly
  • Remember previous passwords to prevent users from reusing old ones
  • Set how often passwords must be changed
These features help keep user accounts more secure by ensuring passwords stay fresh and can't be reused. This helps organizations meet security standards and prevents problems from weak or old passwords.

Configuration and applicability

This feature is available when the passwordhistorycontrol parameter in system settings is enabled. After you enable this feature, the following default values are applied to system parameters:
  • Daystoexpire: 30 (Number of days before the password expires)
  • Warnpriorndays: 5 (Number of days before password expiration when users are warned)
  • pwdhistoryCount: 6 (Number of passwords retained in the history)
Configurability:
  • Daystoexpire and Warnpriorndays can be configured for system groups and can be set or unset when Passwordhistorycontrol is enabled.
  • Once Passwordhistorycontrol is enabled, Daystoexpire, Warnpriorndays, and pwdhistoryCount values in the system parameters cannot be unset.
  • These values cannot be set or unset in system groups or system parameters when the passwordhistorycontrol option is disabled.

Important notes for applying changes

  • To apply changes after enabling Passwordhistorycontrol, you must save the configuration.
  • Once saved, the current user password history is recorded for each partition.
  • After users are required to change their passwords, the new passwords must also be saved to update the password history.
  • If the configuration is saved while Passwordhistorycontrol is disabled, all previous user password history is erased.

Limitation

NetScaler does not support the Password History Control feature when multifactor authentication (MFA) is configured. We recommend you to disable this feature when using MFA.
When attempting to log in through CLI with MFA, the following error is returned if the user name matches a local system user name with an expired password.
"Session Expired or killed. Please log in again."
However, logging in with the same user name through the GUI is successful.

How to configure and use the password rotation and history feature

This section details the steps to configure and manage the password rotation and history feature using both the Command Line Interface (CLI) and the GUI.

Configuration by using the CLI

Enable password history control:
At the command prompt, type:
set system parameter -passwordhistorycontrol ENABLED
Note:
When passwordhistorycontrol is ENABLED, daystoexpire, warnpriorndays, and pwdhistorycount parameters are updated with their default values (30, 5, and 6 respectively).
Update system-wide password parameters (optional):
You can customize the default values for password expiration and history count.
At the command prompt, type:
set system parameter -daystoexpire <days> -warnpriorndays <days> -pwdhistorycount <count>
Example:
set system parameter -daystoexpire 60 -warnpriorndays 10 -pwdhistorycount 3
Note:
After passwordhistorycontrol is ENABLED, daystoexpire, warnpriorndays, and pwdhistorycount values in the system parameters cannot be unset. These values cannot be set or unset when passwordhistorycontrol is DISABLED.
Configure parameters for system groups (optional):
You can also apply password parameters at the system group level.
To add values to a new group:
add system group <group_name> -daystoexpire <days> -warnpriorndays <days>
Example:
add system group sg -daystoexpire 45 -warnpriorndays 15
To update an existing group:
set system group <group_name> -daystoexpire <days> -warnpriorndays <days>
Example:
set system group sg -daystoexpire 30 -warnpriorndays 10
Note:
Values set for a system group apply to system users bound to that group.
Save the configuration:
Once all required configuration changes are made, save the configuration to ensure that the feature begins maintaining user password history for local system users.
Note:
If the user does not have sufficient permission to save the configuration, an administrator must save the changes.
Check user password expiry inheritance:
To see if a user's password expiry parameters are inherited from GLOBAL (system parameter) or GROUP (system group), run:
sh system user
User login behavior:
  • If a user's password is about to expire, a warning message is displayed upon login.
  • Once a user's password has expired, they are forced to change their password during login.
  • If a password being set is a reuse of a previous password (within the history count), a password reuse error message is returned.
  • Upon a successful password change, the user can log in to the command prompt.
Disable the feature:
At the command prompt, type:
set system parameter -passwordhistorycontrol DISABLED
Note:
If the configuration is saved while the feature is DISABLED, all stored user password history is erased.

Configuration by using the GUI

Enable password history control:
  1. Navigate to Configuration > System > Settings.
  2. Click Change Global System Settings.
  3. In the Other Settings section, enable Passwordhistorycontrol.
Set system-wide password parameters (optional):
  1. After enabling Passwordhistorycontrol, configure the following parameters in the Other Settings section:
    • Days to Expire
    • Warn Prior N Days
    • Password History Count
  2. Click OK.
  3. Save the configuration.
Note:
If these parameters are not explicitly updated, default values are applied.
Update parameters for system groups (optional):
  1. Navigate to Configuration > System > User Administration > Groups.
  2. Click Add to create a new group, or Edit to modify an existing one.
  3. Configure the Days to Expire and Warn Prior N Days for the group.
  4. Click Create or OK.
Note:
Values set for a system group apply to system users bound to that group.
Check user password expiry inheritance:
  1. Navigate to Configuration > System > User Administration > Users.
  2. Scroll to the right to find details under Password Expiration Parameters Inherited From.
User login behavior:
  • If a user's password has expired, they are forced to change the password from the GUI during login.
  • If the new password is a reuse of a previous one, the user is redirected to the same page with a password reuse error.
  • Once the new password is accepted, the GUI login is successful.
Note:
If the user does not have sufficient permission to save the configuration after changing their password, an administrator will need to save the changes to maintain the password history.
Disable the feature:
  1. Navigate to Configuration > System > Settings.
  2. Click Change Global System Settings.
  3. In the Other Settings section, select DISABLED for Passwordhistorycontrol.
  4. Click OK.
Important:
If the configuration is saved when the feature is DISABLED, all stored user password history is erased.

Default user account

The nsrecover user account is used by the administrator to recover the NetScaler appliance. You can log on to NetScaler using nsrecover if the default system users (nsroot) are unable to log in due to any unforeseen issues. The nsrecover login is independent of user configurations and lets you access the shell prompt directly. You are always allowed to log in through the nsrecover irrespective of whether the maximum configuration limit is reached.