19.08.2013 Views

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Polycom</strong> <strong>RMX</strong> 1500/<strong>2000</strong>/4000 Administrator’s <strong>Guide</strong><br />

For more information see "Renaming a User” on page 14-7.<br />

Disabling Inactive Users<br />

Users can be automatically disabled by the system when they do not log into the <strong>RMX</strong><br />

application for a predefined period. When the <strong>RMX</strong> is configured to Ultra Secure Mode (the<br />

ULTRA_SECURE_MODE System Flag is set to YES), this option is enforced.<br />

• To enable this option, the DISABLE_INACTIVE_USER System Flag to a value between<br />

1 to 90. This value determines the number of consecutive days a user can be inactive<br />

before being disabled.<br />

When flag value is set to 0 (default in standard security environment), this option is<br />

disabled.<br />

The flag value is automatically set to 30 days when the ULTRA_SECURE_MODE<br />

System Flag is set to YES.<br />

• The user is marked as disabled but is not deleted from the system administrator/<br />

operator database.<br />

• The user remains disabled until re-enabled by an administrator.<br />

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

• The last remaining administrator cannot be disabled.<br />

For more information see "Disabling a User” on page 14-5.<br />

Managing the User Login Process<br />

Implementing Strong Passwords<br />

Strong Passwords can be implemented for logging into the <strong>RMX</strong> management applications.<br />

They can be implemented when the system is in standard security mode or when in Ultra<br />

Secure Mode.<br />

The FORCE_STRONG_PASSWORD_POLICY System Flag, which enables or disables all<br />

password related flags cannot be set to NO and all Strong Passwords rules are automatically<br />

enabled and cannot be disabled when the ULTRA_SECURE_MODE System Flag is set to<br />

YES.<br />

If an administrator modifies any of the Strong Passwords flag settings, all users are forced to<br />

perform the password change procedure, ensuring that all user passwords conform to the<br />

modified Strong Passwords settings.<br />

Administrators can change passwords for users and other administrators. When changing<br />

passwords for him/herself, other administrators or other users, the administrator is<br />

required to enter his/her own administrator’s password.<br />

Strong Passwords rules are enforced according to the settings of the various Strong Passwords<br />

flags as described in Table 21-8, “ULTRA_SECURE_MODE Flag Value – Effect on System<br />

Flags,” on page 21-39. Default settings of these flag change according to the system security<br />

mode.<br />

Password Character Composition<br />

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

— Upper case letters<br />

— Lower case letters<br />

— Numbers<br />

14-10 <strong>Polycom</strong>, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!