| Oracle® Database Advanced Security Administrator's Guide 1 0g Release 1 (10.1) Part Number B10772-01 |
|
|
View PDF< /td> |
Entrust Authority (formerly known as Entrust/PKI) is a suite of PKI products provided by Entrust, Inc., that provides certificate generation, certificate revocation, and key and certificate mana gement. Oracle Advanced Security is integrated with Entrust Authority so both Entrust and Oracle users can enhance their Oracle envir onment security.
This appendix contains the following topics:
Entrust-enabl ed Oracle Advanced Security provides:
Entrust-enabled Oracle Advanced Security supports the use of Entrust creden
tials for X.509-based authentication and single sign-on. Instead of usi
ng an Oracle wallet to hold user PKI credentials, Oracle Advanced Security can access PKI credentials that are created by Entrust Aut
hority and held in an Entrust profile (a.epf file). Users who have deployed Entrust software within their enterprise are
thus able to use it for authentication and single sign-on to Oracle Database.
Entrust-enabled Oracle Advanced Security uses the extensive key management and rollo ver functionality provided by Entrust Authority, which shields users from the complexity of a PKI deployment. For example, users are automatically notified when their certificates are expiring, and certificates are reissued according to preferences that administrato rs can configure.
Entr ust provides a certificate authority component, which natively checks certificate revocation status and enables the revocation of cer tificates.
Users using Entrust credentials for authentication to Oracle are assured that the revocation status of the certificate is checked, and connections are prevented if the certificate is revoked.
< /a>To implement Entrust-enabled O racle Advanced Security, the following system components are required:
|
Note: In the following sections, the term client refers to a client connecting to an Oracle database, and the term server refers to the host on which the Oracle database resides. |
|
Note: Oracle only supports the use of Entrust-enabled Oracle Advanced Security with versions of Entrust Authority Security Manager that run on Oracle Database. |
| See Also:
Chapter 7, "Configuring Secure Sockets Layer Auth entication", for information about certificate authorities. |
Entr ust Authority Security Manager supports unattended login, also called Server Login, which eliminates the need for a Database Administrator (DBA) to repeatedly enter a password for the Entrust profile on t he server. With unattended login, the DBA need only enter a password once to open the Entrust profile for the server to authenticate itself to multiple incoming connections.
Entrust Authority Self-Administration Server is the administrator's secure interface to Entrust Authority Security Manager.
Entrust Entelligence Desktop Manager provides support for user key management and single sign-on functionality on both clients and server by enabling Oracle Database server proces s access to incoming SSL connections.
|
Note:< /strong> Do not install Entrust Entelligence Desktop Manager on the server computer becau
se it uses unattended login credentials files with |
|
Note: Figure F-1 does not include client and server profiles creation, which is presumed. |
Text description of the ill ustration asoag025.gif
| See Also:
strong>
"How SSL Works in an Oracle Environment: The SSL Han dshake" |
This section describes the following tasks, which are required to configure Entrust-enabled Oracle Advanced Secu rity SSL authentication:
This section describes how to create Entrust profiles, which can be created by either administrators or users. On UNIX platforms, administrators create the Entrust profiles for all clients. On Windows platforms, users can create their own Entrust profiles.
Administrators create Entrust profiles as follo ws:
.epf file.Entrust users create thei r own Entrust profiles as follows:
< a name="634737">
Start > Programs
> Entrust > Entrust Profiles >
code> Create Entrust Profiles
For Oracle Advanced Security 10g Release 1 (1 0.1), Entrust support installs in Typical mode. A single Oracle installation supports the use of both Oracle Wallets and Entrust prof iles.
Configure SSL on the cli ent and server.
| See Also:
Chapter 7, "Configuring Secure Sockets Layer Authenticatio n", for information about configuring SSL on the client and server; skip the section that describes the Oracle wallet location. p> |
The steps for configuri ng Entrust on the client vary according to the type of platform:
If the client resides on a non-Windows platform, perform the following steps:
JAVA_HOME variable to the JDK or JRE location.
< a name="634802">
For example:
>sete nv JAVA_HOME $ORACLE_HOME/JRE
WA
LLET_LOCATION in the sqlnet.ora file.
For examp le:
WALLET_LOCATION=
(SOURCE=(METHOD=entr) (METHOD_DATA = (PROFILE=profile_location) (INIFILE=initialization_file_location) ))
If the client resides on a Windows platform, ensure that the Entrust Entelligence Desktop Manager comp onent is installed on the client and perform the following steps to set up the Entrust credentials.
WALLET_LOCATION parameter in the sqlnet.ora fi
le.
For example:
WALLET_LOCATION=
(SOURCE=
(METHOD=entr ) (METHOD_DATA= (INIFILE=initialization_file_location) )
)
where initialization_file_location is the path to the .ini file.
The steps for configuring Entrust on the server vary according t o the type of platform:
If the serve r is a UNIX platform, ensure that the Entrust/Server Login Toolkit component is installed on the server and perform the following ste ps:
| See Also:
"Required System Components for Entrust-Enabled Oracle Advanced Security" a> for information about downloading the Entrust Server Login toolkit. |
WALLET_LOCATION parameter in the sqlnet.ora and
listener.ora files to specify the paths to the server's profile and the Entrust initialization file:
WALLET_LOCATION = (SOURCE = (METHOD = ENTR) (METHO D_DATA = (PROFILE = profile_location) (INIFILE = initialization_file_location) ) )
CLASSPATH environment variable to include the following paths:
$ORACLE_HOME/JRE/lib/rt.jar $ORACLE_HOME/JRE/lib/i18n.jar $ORACL E_HOME/jlib/ewt*.jar $ORACLE_HOME/jlib/help*.jar $ORACLE_HOME/jlib/share*.jar $ORACLE_HOME/jlib/swingall*.jar $ORACLE_HOME/network/jlib/netentrust.jarli>
etbinder command to create unattended login creden
tials, or.ual files by using the following steps:
PATH environment variable to include the path to the etbinder command, which is locate
d in the /bin directory where the Server Login Toolkit is installed.LD_LIBRARY_PATH to include the path to the Entrust libraries.SSL_ENTRUST_INI environment variable to include the full path to the Entrust initialization file.etbinder
A message displays indicating that the credentials file (filename.ual) has been created.
If the server is on a Windows platform, perform the following steps:
| See Also:
"Required System Components for Entrust-Enabled Oracle Advanced Security" for information about downloading Entrust Entelligence Desktop Manager. |
WALLET_LOCATION parameter in the sqlnet.ora and listener.ora files to specify
the paths to the server's profile and the Entrust initialization file:
WALLET_LOCATION =(SOURCE =(METHOD = ENTR) < /a>(METHOD_DATA = (PROFILE = profile_location) (INIFILE = initialization_file_location) ))
.ual extension. Ensure that the owner of the .ual<
/code> file is the same as the owner of the Oracle service.
To run the binder command ch
oose
Start > Programs > Entrust Toolkit > Server Login <
code>>
Entrust Binder
Enter the path to the profile , the password, and the path to the Entrust initialization file. A message informs you that you have successfully created a credentia l file.
Create global users in the database based on the distinguished name (DN) of each Entrust user.
For example:
SQL> create user jdoe identified globally as 'cn=jdoe,o=oracle,c=us';
where "cn=jdoe, o=oracle, c=us" is the Entrust distinguished name of the user.
sqlplus /@net_service_name
where net_service_name is the service name of the Oracle i
nstance.
The Entrust_Login dialog box appears.
WALLET_LOCATION parameter, you are prompted to enter the path to the Entrust initial
ization file.
This section describes how t o diagnose errors returned from Entrust to Oracle Advanced Security users.
You may encounter the following error messages regardless of what platform you are running Entr ust on.
Cause: SQL*Plus login on an Entrust-enabled Oracle client errors out with this gene ric error message. This error can be caused by a number of problems, including the following causes:
Action: To get more detail on the Entrust error, turn on tracing for SQL*Plus and the trace output should ind
icate the Entrust failure code. Enable tracing by specifying the following parameters in the sqlnet.ora file:
On the client:
TRACE_LEVEL_CLIENT=16TRACE_DIRECTORY_CLIENT=&
lt;valid_client_directory_name>TRACE_FILE_CLIENT=
clientTRACE_UNIQUE_CLIENT=ONOn the server:
Search for and locate the string IKMP in the generated trace file. Adjacent to this string, error messages are lis
ted that provide details about the problem you are encountering. This detailed error code information is returned by the Entrust API.
Cause: The WALLET_LOCATION parameter does not specify the Entrust initialization file locat
ion in the client side sqlnet.ora file.
Action: Ensu
re that the location of the Entrust initialization file is specified in the WALLET_LOCATION parameter in the sqlne
t.ora file on the client.
| See A lso: |
|
See Also:
Step 4 of
"Configuring Entrust on a Windows Server" for information about cr
eating a |
.ual) is generated using a valid password. Also, confirm that the versions for Entrust Server Login tool
kit and Entrust IPSEC Negotiator toolkit match (that is, that the IPSec Toolkit 6.0 works with Server Login Toolkit 6.0).IdentityLibrary = location < /a>
where location is the location of libidapi.so, in
cluding the file name.