OpenEdge uses this value to authenticate a user identity only when you call the SECURITY-POLICY:SET-CLIENT( ) method or the
SET-DB-CLIENT function on an unsealed client-principal object, which seals the object and sets the identity in a single, OpenEdge-performed user authentication operation.
Use an encrypted value for this attribute especially when you export the unsealed client-principal to a remote authentication service, or to any other ABL session prior to sealing the object. For more information on exporting a client-principal, see the
EXPORT-PRINCIPAL( ) method entry in this manual.
If your application authenticates the identity, it must also seal the client-principal by calling the
SEAL( ) method before using the object to set the identity. However, the SEAL( ) method does not require any setting of this attribute.
OpenEdge does not store the setting of this attribute. Once the client-principal object is sealed, OpenEdge removes all trace of the attribute value from the client-principal.
There is currently no support for specifying a secondary passphrase value in OpenEdge.