Enhancing Security - Expert Oracle and Java Security - page 277

Listing 11-11. Additions to Client tnsnames.ora File for Wallet

orcl =

(DESCRIPTION=
(SOURCE_ROUTE=YES)
(ADDRESS=(PROTOCOL=tcp)(HOST=orcl.org.com)(PORT=1521))
(CONNECT_DATA=(SERVICE_NAME=ORCL)))

orcl_appver =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST= orcl.org.com)(PORT=1521))
(CONNECT_DATA=
(SERVER=DEDICATED)
(SERVICE_NAME=ORCL)
(SID=ORCL)))

orcl_appusr =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST= orcl.org.com)(PORT=1521))
(CONNECT_DATA=
(SERVER=DEDICATED)
(SERVICE_NAME=ORCL)
(SID=ORCL)))

 Note At least the HOST name will be different in your case, so modify those settings.

Use the Wallet from SQL*Plus
This is the slickest aspect of using the wallet. You can connect to Oracle database without entering the
password, presuming the wallet is created and placed where needed and that your configuration files are
correct. Just enter this SQL*Plus command to connect:
%ORACLE_HOME%\bin\sqlplus /@orcl_appusr
Keep in mind that the password is acquired somehow through the wallet; therefore, it still exists on
the client. One might examine the computer memory during processing to capture the clear text
password as it is acquired from the wallet. One might also examine the Java code, obfuscated Java code,
DLLs, and obfuscated DLLS used by Oracle database to maintain and use the wallet, thereby revealing
the process for independently deciphering the wallet password. I don't pretend to know how difficult
that would be.

Use the Wallet from Java
Using the client wallet for authentication in a Java application requires an additional jar file in your
CLASSPATH . The oraclepki.jar file is required for reading the wallet files. On the command line, you can
run a test in the Chapter11/wallet folder.