General Checklist For Running Entrust On Any Platform - Oracle Database B10772-01 Administrator's Manual

Search for and locate the string "fail" or "ntz*" function calls. Adjacent to these,
error messages are listed that provide details about the problem you are
encountering.

General Checklist for Running Entrust on Any Platform

The following items apply to all platforms:
1.
2.
3.
4.
5.
Confirm that the Entrust Authority is online.
Confirm that the .ual file is generated. These files are created for unattended
login credentials.
Oracle recommends that you generate an unattended login
Note:
credential file (.ual file) for the server only. If you generate a .ual
file for the server only, then when users attempt to log in, they are
presented a GUI that prompts them for their password and their
Entrust profile name. After users supply this information, the
connection request is forwarded to the Entrust server, which looks
up the revocation file and the .ual file to determine the
permissions for granting the request.
Confirm that the Entrust initialization file contains the following entry in the
first section that specifies the Entrust Settings:
IdentityLibrary=location
The full path to the location of the libidapi.so file should be specified in the
IdentityLibrary parameter. This parameter setting enables generating a
.ual file on the server.
Ensure that all Entrust toolkits, including the Entrust IPSEC Negotiator toolkit
and the Server Login toolkit, are the same version so they are compatible.
Ensure that you have specified TCP/IP with SSL in the
SQLNET.AUTHENTICATION_SERVICES parameter in the sqlnet.ora file as
shown in the following example:
SQLNET.AUTHENTICATION_SERVICES=(tcps, authentication_type1, authentication_
type2)
Troubleshooting Entrust In Oracle Advanced Security
Entrust-Enabled SSL Authentication F-17