G06.31 Software Installation and Upgrade Guide

G06.31 Installation and Fallback Alerts
G06.31 Software Installation and Upgrade Guide544626-002
2-20
Safeguard Password Enhancements (G06.31)
5. If new users were added to the system after PASSWORD-ALGORITHM was
changed to HMAC256, the system administrator must reset their passwords to
enable them to log into the system. Otherwise, the users cannot access the system
after fallback.
Migration With Standard Security (Safeguard Not Installed)
Once the new version is installed, use the new PWCONFIG utility to modify the
appropriate attributes if you do not want to accept the new default values.
Fallback With Standard Security (Safeguard Not Installed)
In all cases, install the previous version of Standard Security.
If ENCRYPTPASSWORD is OFF or ALGORITHM is set to DES, no extra fallback
steps are required.
If ALGORITHM is set to HMAC256:
When users first change their password after HMAC256 is enabled, they must
remember their immediate previous password.
After fallback, users must use their old password to log into the system if:
°
Their user account existed before the installation of the H03 version of
Standard Security.
or
°
They are new users whose password was encrypted in DES or not encrypted
at all before ALGORITHM was changed to HMAC256.
If users were added to the system after ALGORITHM was changed to HMAC256,
they must use a blank password to log into the system.
Safeguard Password Enhancements (G06.31)
Starting with the versions of Safeguard (T9750G07^AFI) and Standard Security
(T6533G06^ABS) released with the G06.31 RVU, the following password
enhancements are supported:
The maximum allowed Safeguard password length is increased from 8 bytes to 64
bytes.
Passwords can contain embedded spaces.
New password quality attributes are introduced.
Maximum Password Length Increased
The maximum allowed password length is increased from 8 bytes to 64 bytes. The
following new configuration attributes are introduced to facilitate the longer password