H06.10 Release Version Update Compendium

the user/alias. In previous versions, these attributes could not be reset unless the user/alias was
deleted and re-created.
New User/Alias Attribute
A new user/alias attribute, STATIC-FAILED-LOGON-RESET-TIME, is introduced. This attribute
indicates the time at which the values of the attributes STATIC FAILED LOGON COUNT and
LAST-UNSUCCESSFUL-ATTEMPT were last reset. This attribute cannot be modified; it can only
be viewed by the detailed output of the Safecom INFO User/Alias command.
New RESET-STATIC-FAILED-LOGON-COUNT Attribute
The new RESET-STATIC-FAILED-LOGON-COUNT attribute resets the value of STATIC FAILED
LOGON COUNT to zero and LAST-UNSUCCESSFUL-ATTEMPT to *NONE*, This attribute is
accepted only for an ALTER User/Alias command.
New SPI Tokens
The following new SPI tokens are introduced:
• ZSFG-TKN-RESET-STATIC-FAILLOG, token type ZSPI-DDL-BOOLEAN. This token is
valid with the ZCOM-CMD-ALTER command for the objects ZCOM-OBJ-USER and
ZCOM-OBJ-ALIAS.
• ZSFG-TKN-FAILLOGCOUNTRESETTIME, token type ZSPI-TYP-TIMESTAMP. The value
of this token can be obtained by the ZCOM-CMD-INFO command for the objects
ZCOM-OBJ-USER and ZCOM-OBJ-ALIAS, as a token in the response buffer.
New Field in User_SubrecExt_1
A new field in the user profile subrecord User_SubrecExt_1 is introduced as part of the Safeguard
audit record changes. The name of the new field is zfailedlogoncountresettime. The field indicates
the time at which the values of the attributes STATIC FAILED LOGON COUNT and
LAST-UNSUCCESSFUL-ATTEMPT were last reset.
Migration in a Safeguard Environment
There are no special considerations for migrating to the new version of Safeguard. However,
you can use the following mitigation procedure to handle any unexpected failures that occur
during migration. This procedure preserves the user or password database that is needed to
restore the original user or alias database.
1. Use VPROC to determine the current versions of:
OSMP
OSMON
SAFEART
SAFECOM
2. Back up the current Safeguard files ($*.SAFE.*, $SYSTEM.SYSTEM.USERID, and
$SYSTEM.SYSTEM.USERAX)_
3. Use SAFECOM to create an Obey file to save the current policy.
To create an Obey file, do the following in SAFECOM:
TACL> safecom/out.$system.safe.safevalu/
=display as commands on
=info safeguard, detail
The output from these commands is retained in a file named SAFEVALU, located in
$SYSTEM.SAFE. Run this file in SAFECOM to restore the settings after migration.
For more information, see Chapter 10 of the Safeguard Administrator's Manual.
20 Manageability Products