Note: DO NOT put an encrypted value from an application
in the password attribute to be passed up in a populate
operation.
For more information, see the The Default Policy Record and
waddprop, waddusrprop, wgenusrdef section in the Tivoli
SecureWay User Administration Management Guide. For details
about using the waddprop and waddusrprop commands, see the
Tivoli SecureWay User Administration Reference Manual.
3. After adding an attribute to the profile default policy record, you
must use the wchgusrprop command to set flags that determine
how the attribute will be treated by Tivoli SecureWay User
Administration. The l option sets the UserProfile_a_login flag,
which sets the attribute to the same value as common login
whenever common login changes. The p option sets the
UserProfile_a_password flag, which sets the attribute to the
same value as common password whenever common password
changes, and encrypts that value.
The following example specifies that the first attribute added in
the Step 2 example should be treated as a login:
wchgusrprop -l -t ora8 @UserProfile:Oracle_Users \
login ""
Similarly, the following example specifies that the second
attribute added in the Step 2 example should be treated as a
password:
wchgusrprop -p -t ora8 @UserProfile:Oracle_Users \
login ""
For details about using the wchgusrprop command, see the
Tivoli SecureWay User Administration Reference Manual.
After defining the custom application attributes, you need to set up
the application configuration using the Application Management
Toolkit graphical user interface (GUI), as explained in the following
section.
Note: The Tivoli SecureWay User Administration GUI does not
contain a way to access application-specific attributes. If
Using Supplied Attributes or Creating New Ones
53
Tivoli® SecureWay Application Management Toolkit Guide