Silicon Graphics Gauntlet, Administrator'S Manual

Page: 209 / 306

Managing Users
183
3. Enter the strong-authentication protocol for this user. Valid options are:
4. Leave the password for this user empty. The authentication server uses the value
registered with the appropriate server.
5. Make the information active by saving these changes (in the gauntlet-admin and
gauntlet-gui menuing systems) or exiting the authentication server.
Creating Users with Access Key II
To create a user with Access Key II authentication, use this procedure:
1. Create a key for the Access Key II according to the documentation included with the
key. This creates the keyfile.log file which contains the key.
2. Log in to the firewall and become root.
3. Copy this file to a temporary directory (such as/tmp/vasco) on the firewall.
4. Load the key information into the user authentication management system using
the key initialization tool (/usr/etc/vasco_init)
firebird# vasco_init /tmp/vasco/keyfile.long
This tool creates a user in the authentication management system and loads the key
for this user. It creates the user name by prepending the letter i to the serial number
for that Access Key II. This user is initially disabled.
If you are using multiple authentication servers, or are running your authentication
server under a different name, consult the vasco_init(8) reference page for
additional command line options.
5. Note the user name that the initialization program displays so that you can change
it to something easier for the user to remember.
record loaded for user: i2-0005899-4
6. Use and authentication management tool to change the name of the user:
authmgr->rename i2-0005899-for john ‘John Whorfin’
protocol value
Safeword Authentication Server Safeword
SecurID SecurID