Modifying the value of userPassword checks two password policy settings:

•The password minimum age policy is activated. If the minimum age requirement has not been satisfied, the server returns a [constraintViolation] error. The password update operation fails.

•The password history policy is activated. If the new value of userPassword is in the password history, or if it is the same as the current password, the server returns a [constraintViolation] error. The password update operation fails.

Both adding and modifying the value of userPassword checks password policies set for the password syntax:

•The password minimum length policy is activated. If the new value of userPassword is less than the required minimum length, the server returns a [constraintViolation] error. The password update operation fails.

•The password syntax checking policy is activated. If the new value of userPassword is the same as another attribute of the entry, the server returns a [constraintViolation] error. The password update operation fails.

8.6.2Password policy attributes

The following sections describe the attributes to create a password policy for the server:

•“Password change after reset”

•“User-defined passwords”

•“Password expiration”

•“Expiration warning”

•“Grace login limit”

•“Password syntax checking”

•“Password length”

•“Password minimum age”

•“Password history”

•“Password storage schemes”

Refer to the HP-UX Directory Server administrator guide for instructions on how to set these attributes.

8.6.2.1 Password change after reset

The Directory Server password policy can specify whether users must change their passwords after the first login or after the password has been reset by the administrator.

The default passwords set by the administrator typically follow a company convention, such as the user's initials, user ID, or the company name. If this convention is discovered, it is usually the first value that a cracker uses in an attempt to break into the system. It is therefore recommended that users be required to change their password after it has been reset by an administrator. If this option is configured for the password policy, users are required to change their password even if user-defined passwords are disabled.

If users are not required or allowed change their own passwords, administrator-assigned passwords should not follow any obvious convention and should be difficult to discover.

The default configuration does not require that users change their password after it has been reset.

Refer to “User-defined passwords” for more information.

8.6.2.2User-defined passwords

The password policy can be set either to allow or not to allow users to change their own passwords. A good password is the key to a strong password policy. Good passwords do not

8.6 Designing a password policy 113