c.    If support for password pre-expiration is needed, a name for that attribute and its values that signify whether to enable or disable pre-expiration must be determined. d.    Use the  waddusreptype  command to create the new endpoint type. The following example adds an endpoint type for an Oracle application and enables support for changing passwords using the  wpasswd  command: waddusreptype -e ora8 -n "Oracle8i" -p ora8_ \ -l ora8_login -w ora8_password where  ora8  is the chosen endpoint type code,  Oracle8i  is the chosen endpoint type name,  ora8_login  and  ora8_password are the login and password attribute names, and no password pre-expiration attribute is needed. Notes: 1)    Unless you set the password attribute with the waddusreptype  –w  command option, the  wpasswd command will not function for the endpoint. 2)    Use the  wlsusrprop  p  command option to check a user profile containing application attributes to ensure that the password attribute is set. For more information, see the section on passwords and endpoint types in the  Tivoli SecureWay User Administration Management Guide. For details about using the  wlsusreptype, waddusreptype, and  wpasswd  commands, see the  Tivoli SecureWay User Administration Reference Manual. 2.    Add all of the attributes needed for your custom application to the required profiles using the  waddprop  or  waddusrprop command. There are significant differences between these commands: ¶   Use the waddprop command to add attributes to the profile default policy record and to every record in the profile. If the attributes are needed as arguments for your toolkit application, you should use this command. Otherwise, you should probably use the  waddusrprop  command. Using Supplied Attributes or Creating New Ones 51 Tivoli®  SecureWay Application Management Toolkit Guide