Orapki, TCPS and Oracle SSL

Procedure
Configure your database server to use an Oracle Wallet that includes an SSL certificate for authentication.

Modify the Oracle database user so that the user can be identified by an SSL certificate. Run the following command from Oracle bin directory:
sqlplus / as sysdba
alter user wcs identified externally as ‘CN=oracleuser';
quit;Copy
Note
If your server tier is the same as your client tier, ensure that your user DN is the same as your server tier. For example,
alter user wcs identified externally as ‘CN=server';Copy
Create an Oracle Wallet with the Oracle orapki utility. In a command-line utility, run the following command from Oracle bin directory:
orapki wallet create -wallet wallet_directory -auto_login -pwd wallet_passwordCopy
Where
wallet_directory is the directory where you want to create the Wallet. For example, c:\server.wallet.
Note
Ensure that the directory that you set as the wallet_directory is readable and executable by the appropriate users.
wallet_password is the password that you want to set for the Wallet. For example, s3rv3rp45s.
For example,
orapki wallet create -wallet c:\server.wallet -auto_login -pwd s3rv3rp45sCopy
Install the certificate that is issued by the certificate authority. For more information about creating a certificate request and installing the certificate, see Oracle Technology Network. As an example for testing purposes, add a self-signed certificate to your Oracle Wallet for use as the database server certificate. In a command-line utility, run the following command from Oracle bin directory:
orapki wallet add -wallet wallet_directory -dn “dn_name” -keysize 1024
-self_signed -validity 365 -user_cert -trusted_cert -pwd wallet_passwordCopy
Where
wallet_directory is the directory where you want to create the Wallet. For example, c:\server.wallet.
dn_name is the distinguished name of the certificate owner, which is the database server name. For example, CN=server.
wallet_password is the password that you want to set for the Wallet. For example, s3rv3rp45s.
For example,
orapki wallet add -wallet c:\server.wallet -dn “CN=server” -keysize 1024 -self_signed -validity 365 -user_cert -trusted_cert -pwd s3rv3rp45sCopy
Export the SSL certificate for the database server tier. In a command-line utility, run the following command from Oracle bin directory:
orapki wallet export -wallet wallet_directory -dn “dn_name”
-cert certificate_file -pwd wallet_passwordCopy
Where
wallet_directory is the directory where you want to create the Wallet. For example, c:\server.wallet.
dn_name is the distinguished name of the certificate owner, which is the database server name. For example, CN=server.
certificate_file is the path and name of the file that is to include the certificate that you are exporting. For example, c:\server.cert.
wallet_password is the password that you want to set for the Wallet. For example, s3rv3rp45s.
For example,
orapki wallet export -wallet c:\server.wallet -dn “CN=server” -cert c:\server.cert -pwd s3rv3rp45sCopy
Configure your client tier to create an Oracle Wallet that includes the database server SSL certificate and an SSL certificate for authenticating users.

Note
If the client tier where users run WebSphere Commerce utilities is the same as your database server tier, skip to step 12.
Create an Oracle Wallet with the orapki utility in your client environment. In a command-line utility, run the following command from Oracle bin directory:
orapki wallet create -wallet c:\client.wallet -auto_login -pwd cl13ntp45sCopy
Import the SSL certificate from your server tier. In a command-line utility, run the following command from Oracle bin directory:
orapki wallet add -wallet wallet_directory -trusted_cert
-cert certificate_file -pwd wallet_passwordCopy
Where
wallet_directory is the directory where you want to create the Wallet. For example, c:\client.wallet.
certificate_file is the path and name of the file that is to include the certificate that you are exporting. For example, c:\server.cert.
wallet_password is the password that you want to set for the Wallet. For example, cl13ntp45s.
For example,
orapki wallet add -wallet c:\client.wallet -dn “CN=server” -cert c:\server.cert -pwd cl13ntp45sCopy
Update the Oracle sqlnet.ora configuration file for your client.
Go to the following directory and open the sqlnet.ora file for editing:
LinuxORACLE_HOME/network/admin
WebSphere Commerce DeveloperORACLE_HOME\network\admin
Where ORACLE_HOME is the root directory for your Oracle database. For example, C:\ORACLE\ORA92.
Update the configuration parameters to match the settings for your system. When you are updating the file, ensure that you update the following parameters:
SQLNET.AUTHENTICATION_SERVICES
SSL_CLIENT_AUTHENTICATION
SSL_VERSION
NAMES.DIRECTORY_PATH
WALLET_LOCATION
For example, your parameters can resemble the following code snippet:
SQLNET.AUTHENTICATION_SERVICES = (TCPS, BEQ, NTS)
SSL_VERSION = 3.0
NAMES.DIRECTORY_PATH = (TNSNAMES, EZCONNECT)
WALLET_LOCATION =
(SOURCE =
(METHOD = FILE)
(METHOD_DATA =
(DIRECTORY = c:\client.wallet)
)
)
SSL_CLIENT_AUTHENTICATION = TRUECopy
Update the Oracle tnsnames.ora configuration file.
Go to the following directory and open the tnsnames.ora file for editing:
LinuxORACLE_HOME/network/admin
WebSphere Commerce DeveloperORACLE_HOME\network\admin
Where ORACLE_HOME is the root directory for your Oracle database. For example, C:\ORACLE\ORA92.
Add a TNS entry that points to your database server. For example, your configuration can resemble the following code snippet:
WCS =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCPS)(HOST = fahadjwcs.canlab.ibm.com)(PORT = 2484))
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = WCS)
)
)Copy
Install the certificate that is issued by the certificate authority. For more information about creating a certificate request and installing the certificate, see Oracle Technology Network. As an example for testing purposes, add a self-signed certificate to the client tier Wallet for use as the user certificate. If your client is the same as your server, add the certificate to your server tier Wallet. In a command-line utility, run the following command from Oracle bin directory:
orapki wallet add -wallet wallet_directory -dn “dn_name” -keysize 1024 -self_signed
-validity 365 -user_cert -trusted_cert -pwd wallet_passwordCopy
Where
wallet_directory is the directory where you want to create the Wallet. For example, c:\client.wallet.
dn_name is the distinguished name of the certificate owner, which is the database server name. For example, CN=server.
wallet_password is the password that you want to set for the Wallet. For example, cl13ntp45s.
For example,
orapki wallet add -wallet c:\client.wallet -dn “CN=oracleuser” -keysize 1024 -self_signed
-validity 365 -user_cert -trusted_cert -pwd cl13ntp45sCopy
Export the user SSL certificate from the client tier Oracle Wallet. In a command-line utility, run the following command from Oracle bin directory:
orapki wallet export -wallet c:\client.wallet -dn “CN=oracleuser” -cert c:\user.cert -pwd cl13ntp45sCopy
Continue the configuration for your database server tier.

Import the user SSL certificate from your client tier Oracle Wallet into the server tier Oracle Wallet. In a command-line utility, run the following command from Oracle bin directory:
orapki wallet add -wallet c:\server.wallet -trusted_cert -cert c:\user.cert -pwd s3rv3rp45sCopy
Shut down your Oracle database by running the following command from Oracle bin directory:
sqlplus / as sysdba
shutdown immediate;
quit;Copy
Stop the Oracle listener with the Oracle Listener Control utility by running the following command from Oracle bin directory:
lsnrctl stopCopy
Update the Oracle listener listener.ora configuration file.
Go to the following directory and open the listener.ora file for editing:
LinuxORACLE_HOME/network/admin
WebSphere Commerce DeveloperORACLE_HOME\network\admin
Where ORACLE_HOME is the root directory for your Oracle database. For example, C:\ORACLE\ORA92
Update the listener parameters to match the settings for your system. When you are updating the file, ensure that you update the parameters in the following sections:
SID_LIST_LISTENER
LISTENER
WALLET_LOCATION
SSL_CLIENT_AUTHENTICATION
For example, your updated keys can resemble the following code snippet:
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = WCS)
(SID_NAME = WCS)
(ORACLE_HOME = Oracle_installdir\dbhome_1)
)
)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCPS)(HOST = myhostname.mycompany.com)(PORT = 2484))
)
)
WALLET_LOCATION =
(SOURCE =
(METHOD = FILE)
(METHOD_DATA =
(DIRECTORY = C:\server.wallet)
)
)
SSL_CLIENT_AUTHENTICATION = TRUECopy
Update the Oracle sqlnet.ora configuration file.
Go to the following directory and open the sqlnet.ora file for editing:
LinuxORACLE_HOME/network/admin
WebSphere Commerce DeveloperORACLE_HOME\network\admin
Where ORACLE_HOME is the root directory for your Oracle database. For example, C:\ORACLE\ORA92.
Update the configuration parameters to match the settings for your system. When you are updating the file, ensure that you update the following parameters:
SQLNET.AUTHENTICATION_SERVICES
SSL_CLIENT_AUTHENTICATION
SSL_VERSION
NAMES.DIRECTORY_PATH
WALLET_LOCATION
For example, your parameters can resemble the following code snippet:
SQLNET.AUTHENTICATION_SERVICES = (BEQ, TCPS, NTS)
SSL_CLIENT_AUTHENTICATION = FALSE
SSL_VERSION = 3.0
NAMES.DIRECTORY_PATH = (TNSNAMES, EZCONNECT)
WALLET_LOCATION =
(SOURCE =
(METHOD = FILE)
(METHOD_DATA =
(DIRECTORY = C:\server.wallet)
)
)Copy
Restart the Oracle listener by running the following command from Oracle bin directory:
lsnrctl startCopy
Start your Oracle database by running the following command from Oracle bin directory:
sqlplus / as sysdba
startup;
quit;Copy
Configure the AllDBConnector class configuration for establishing a database connection for WebSphere Commerce utilities to use the certificate in the Oracle Wallet.

Update the database connection acquisition configuration file to ensure that the WebSphere Commerce utilities can authenticate users through the Oracle Wallet.
Go to the following directory and open the alldbconnector.xml configuration file for editing.
WebSphere Commerce DeveloperWCDE_installdir\WC\xml\config
Update the alldbconnector.xml file to include two overrides to configure how utilities authenticate users. In the first override configuration, you must configure the override for your local client database. In the second override configuration, configure the connection override properties for your production environment database. This second override configuration ensures that utilities can use the SSL certificates to authenticate users when a utility, such as the stagingprop utility, must connect to multiple databases.
Note
For the override property identifier, oradestwallet, a corresponding TNS entry, WCSDEST, must exist in the tnsnames.ora configuration file for your utility client environment.
For more information about the properties that you can include in your override configuration in the alldbconnector.xml file, see Database connection acquisition for utilities and Ant tasks.

If your Oracle database driver type is a thin driver, your updated AllDBConnector class configuration in the alldbconnector.xml file can resemble the following code snippet:















Copy
If your Oracle database driver type is a thick driver, your updated AllDBConnector class configuration in the alldbconnector.xml file can resemble the following code snippet:















Copy
Where
orasrcwallet is the identifier of the override configuration for your authoring or staging environment.
oradestwallet is the identifier of the override configuration for your production environment.
wallet_directory is the directory that includes the Wallet. For example, c:\server.wallet.

Leave a Reply