Polycom 2000/4000 manual Managing the User Login Process, Implementing Strong Passwords, 11-12

Chapter 11-Users, Connections and Notes

•The user is marked as disabled but is not deleted from the system administrator/operator database.

•The user remains disabled until re-enabled by an administrator.

•If a disabled user attempts to Login, an error message, Account is disabled, is displayed.

•The last remaining administrator cannot be disabled.

For more information see "Disabling a User” on page 11-6.

Managing the User Login Process

Implementing Strong Passwords

Strong Passwords can be implemented for logging into the RMX management applications. They can be implemented when the system is in standard security mode or when in Enhanced Security Mode.

The FORCE_STRONG_PASSWORD_POLICY System Flag, which enables or disables all password related flags cannot be set to NO and all Strong Passwords rules are automatically enabled and cannot be disabled when the JITC_MODE System Flag is set to YES.

If an administrator modifies any of the Strong Passwords flag settings, all users are forced to perform the password change procedure, ensuring that all user passwords conform to the modified Strong Passwords settings.

Administrators can change passwords for users and other administrators. When changing passwords for him/herself, other administrators or other users, the administrator is required to enter his/her own administrator’s password.

Strong Passwords rules are enforced according to the settings of the various Strong Passwords flags as described in Table 16-5, “JITC_MODE Flag Value

–Effect on System Flags,” on page 16-30. Default settings of these flag change according to the system security mode.

Password Character Composition

•A Strong Password must contain at least two of all of the following character types:

—Upper case letters

—Lower case letters

—Numbers

—Special characters: @ # $ % ^ & * ( ) _ - = + } { : " \ ] [ ; / ? > < , . (space) ~

11-12