You can use any format of the “truststore” provided you specify the provider of said format.

The server configuration remains unchanged in this implementation. In this implementation, any Cipher Suite except Diffie-Hellman anonymous authentication can be used. “(SSL_DH_anon_WITH_3DES_EDE_CBC_SHA, SSL_DH_anon_WITH_RC4_128_MD5,Ĭonnection conn=DriverManager.getConnection(url,props) Implementation 2: Use SSL for Encryption and Server Authentication While you don’t have to configure the “truststore” or “keystore,” you do need to force the Cipher Suite to use Diffie-Hellman anonymous authentication:

You also need to turn off SSL client authentication in sqlnet.ora: WALLET_LOCATION=(SOURCE=(METHOD=FILE)(METHOD_DATA=(DIRECTORY=/server/wallet/path))) LISTENER = (ADDRESS_LIST= (ADDRESS=(PROTOCOL=tcps)(HOST=servername)(PORT=2484)) )

You need to configure the “listener” to switch off client authentication: However, this doesn’t mean there will be no authentication in the Oracle database, but rather the authentication will have to be done another way. Using Diffie-Hellman anonymous authentication will cause the server and the client not to be authenticated via SSL. There are three Cipher Suites available for this: In the most basic implementation where you want to use SSL for encryption only, you must use what is called “Diffie-Hellman anonymous authentication” or else the connection will fail. Implementation 1: Use SSL for Encryption Only Today we’re going to take a quick look at how to activate SSL in a number of configurations in Oracle JDBC Thin Driver. In ssl certificates A quick guide on how to activate SSL in Oracle JDBC Thin DriverĪctivating SSL in Oracle JDBC Thin Driver is an extremely important step in enacting a much larger, more comprehensive advanced security implementation.

Java oracle jdbc thin client example