Autonomous Database mandates a secure connection that uses Transport Layer Security (TLSv1.2).

Java applications that use JDBC Thin driver connect with one of the following:

• Mutual TLS (mTLS) Authentication: requires either Oracle Wallet or Java KeyStore (JKS) where both the client and Autonomous Database authenticate each other.

  The wallet and keystore files are included in the client credentials .zip file that is available by clicking Database connection on the Oracle Cloud Infrastructure Console

• TLS Authentication: The client computer matches the server’s CA root certificate against the client’s list of trusted CAs. If the issuing CA is trusted, the client verifies that the certificate is authentic. This allows the client and Autonomous Database to establish the encrypted connection before exchanging any messages.

See Connecting to Oracle Database Manually for additional information on how to connect your Java applications to Autonomous Database using Oracle JDBC driver and Universal Connection Pool.

• JDBC Thin Connections with a Wallet (mTLS)
  Autonomous Database mandates a secure connection that uses Transport Layer Security (TLSv1.2). Depending on the network configuration options, Autonomous Database supports mTLS and TLS authentication.
• JDBC Thin Connections Without a Wallet (TLS)
  Autonomous Database mandates a secure connection that uses Transport Layer Security (TLSv1.2). Depending on the configuration options, Autonomous Database supports mTLS and TLS authentication. This section covers using JDBC Thin Connections with TLS authentication without a wallet.