Oracle Database 19c Release Update 19.32 introduced support for TLS 1.3, post-quantum cryptography (PQC), and FIPS 140-3 mode through its new cryptographic provider. In this blog, we explain how customers can migrate to the new provider while maintaining compatibility with existing TLS 1.2 clients.

The big difference is the introduction of a cryptographic provider framework that supports two providers—Legacy and Next Generation—and allows switching between them. The Next Generation cryptographic provider supports TLS 1.2 and 1.3, PQC key exchange, and FIPS 140-3. It also removes support for older TLS protocols, including TLS 1.0 and TLS 1.1.

Compared with TLS 1.2, TLS 1.3 can reduce connection-establishment overhead by reducing handshake round trips. To adopt TLS 1.3, just patch your database server to Release Update 19.32, and switch to the new cryptographic provider. TLS 1.2, TLS 1.3, and post-quantum cryptography (PQC) hybrid key exchange are available by default. As the server continues to support TLS 1.2, clients using TLS 1.2 do not require immediate updates. Depending on your compliance requirements, you can also enable FIPS 140-3.

Switch to the Next Generation cryptographic provider

After applying Release Update 19.32, the Legacy provider remains the default to support the existing behavior.

To add support for the new cryptographic protocols, switch to the new Next Generation provider. First, shut down the database instance and stop the listener. Then run the following command as the Oracle software owner from the Oracle Home:

python $ORACLE_HOME/bin/crypto_provider.py next-generation

When the database instance and listener are restarted, the new Next Generation cryptographic provider is loaded automatically.

Confirm the selected provider is in use.

python "$ORACLE_HOME/bin/crypto_provider.py" status

The expected status is:

Current cryptographic provider is: Next Generation

Connect with an existing TLS 1.2 client and run the verification query to confirm that the TLS 1.2 connection still works.

SELECT
SYS_CONTEXT('USERENV', 'NETWORK_PROTOCOL') AS network_protocol,

SYS_CONTEXT('USERENV', 'TLS_VERSION') AS tls_version,
SYS_CONTEXT('USERENV', 'TLS_CIPHERSUITE') AS tls_ciphersuite,
FROM dual;

A successful TLS 1.2 connection should show:

  • NETWORK_PROTOCOL = tcps
  • TLS_VERSION = TLS 1.2
  • The output should show a TLS 1.2 cipher suite negotiated by the client and server

As the new cryptographic provider supports both TLS 1.2 and TLS 1.3, existing TLS 1.2 clients can migrate on their own timetable.

Using TLS 1.3

With the new provider active, TLS 1.3 is enabled on the server side, but for TLS 1.3 to be used between the client and the server, the client also needs to support it. If the client supports both TLS 1.2 and TLS 1.3, Oracle Database will automatically select the highest mutually supported protocol version and TLS cipher suite.

If you want to exclusively use TLS 1.3, the TLS_VERSION parameter in sqlnet.ora and listener.ora can be used to specify the TLS versions supported by the server. We recommend leaving these parameters unset so that the strongest mutually supported TLS version is selected automatically without impacting your TLS 1.2 clients.

Note that the SSL_ parameters are deprecated in favor of TLS_. For example, SSL_VERSION is being replaced by TLS_VERSION.

Client support for TLS 1.3 depends on the driver type, the runtime environment such as JDK or .NET, and client configuration in sqlnet.ora. All Oracle Database 26ai clients already support TLS 1.3. Current Oracle Database 19c clients that support TLS 1.3 include:

  • JDBC 19c supports TLS 1.3 through JDK 11 and later
  • OCI-based drivers 19.32 and later require switching to the new cryptographic provider
  • ODP.NET 19c (19.16 and later)

For OCI-based client drivers 19.32 and later, switch to the new cryptographic provider by running the following command in the client’s $ORACLE_HOME.

python $ORACLE_HOME/bin/crypto_provider.py next-generation

Then restart the client application and reconnect.

To confirm that the server supports TLS 1.3, connect with a TLS 1.3-capable client over TCPS and run the verification query as before. A successful TLS 1.3 connection should show:

  • NETWORK_PROTOCOL = tcps
  • TLS_VERSION = TLS 1.3
  • The output should also show a TLS 1.3 cipher suite negotiated by the client and server. TLS_AES_256_GCM_SHA384 is the recommended TLS 1.3 cipher suite.

Harden existing TLS 1.2 with stronger cipher suites

While you may take more time to upgrade the clients to support TLS 1.3, consider removing older TLS 1.2 cipher suites and configuring cipher suites recommended in the applicable Oracle Database documentation through the TLS_CIPHER_SUITES parameter in the server’s sqlnet.ora and listener.ora. To support both TLS 1.2 and TLS 1.3, include the recommended cipher suites for both versions.

TLS_CIPHER_SUITES = (TLS_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)

See TLS 1.2 cipher suites and TLS 1.3 cipher suites for a list of approved cipher suites.

You can also make these changes to sqlnet.ora on the client side to ensure that the client only uses strong cipher suites. For pre-19.32 clients and servers, please set the SSL_CIPHER_SUITES parameter in the sqlnet.ora file.

Post-Quantum Cryptography (PQC)

To address future quantum decryption risk, commonly described as “harvest now, decrypt later”, the new cryptographic provider in Release Update 19.32 supports ML-KEM, a post-quantum key-encapsulation mechanism standardized by the National Institute of Standards and Technology (NIST), and hybrid key establishment, which combines ML-KEM with established cryptographic methods for key exchange. Note that hybrid key establishment is used by default when both client and server are configured with TLS 1.3 and support it. No additional steps are needed. TLS 1.3 remains available for clients that do not support PQC hybrid key establishment.

Enable FIPS 140-3

Complete this step only if your organization requires FIPS 140-3. Starting September 21, 2026, NIST recommends that all new projects use FIPS 140-3.

FIPS 140-3 supports a more limited but stronger set of cryptographic algorithms than those supported in FIPS 140-2 and non-FIPS mode. For example, FIPS 140-3 disallows TLS certificates signed with SHA-1 or MD5. It also disallows legacy encryption algorithms such as 3DES, DES, and RC4.

FIPS mode is enabled through the fips.ora configuration file on the server. Verify that the fips.ora file is in a path defined by the $FIPS_HOME environment variable or in the default location $ORACLE_HOME/ldap/admin.

Set both parameters in the fips.ora file:

FIPS_140 = TRUE
FIPS_140_3 = TRUE

Setting only FIPS_140 = TRUE enables FIPS 140-2 rather than FIPS 140-3.

Support for FIPS 140-3 is provided through Oracle’s OpenSSL FIPS module, which is in the NIST Cryptographic Module Validation Program (CMVP). A modules-in-process listing does not constitute final FIPS 140-3 validation. Enabling FIPS mode does not independently establish compliance with applicable regulatory requirements.

Reverting to the Legacy crypto provider

If you need to use legacy algorithms that are not supported by the Next Generation cryptographic provider, you can revert to the Legacy provider by shutting down the database instance and listener, and then running:

python $ORACLE_HOME/bin/crypto_provider.py legacy

Restart the database instance and listener after reverting and verify the active provider:

python $ORACLE_HOME/bin/crypto_provider.py status

The expected status is:

Current cryptographic provider is: Legacy

If you need to revert to the Legacy provider in OCI-based client driver version 19.32, follow the same steps above on the client.

Summary

With the Next Generation cryptographic provider, TLS 1.3 and hybrid PQC key exchange are enabled by default for supported configurations. After applying 19.32, customers can switch to the new cryptographic provider, restart the database instance and listener, and validate client connectivity. Customers can adopt TLS 1.3 while maintaining compatibility with supported TLS 1.2 clients. FIPS 140-3 mode can be configured where applicable, subject to the documented requirements and limitations.

Related documentation

For TLS deployments, driver-specific requirements, explicit cipher-suite configuration, PQC, FIPS 140-3, and additional deployment scenarios, refer to the following:

Oracle Database 19c Security Guide – Configuring Transport Layer Security Encryption

TLS 1.2 cipher suites and TLS 1.3 cipher suites

Client driver and runtime-specific compatibility for PQC and TLS 1.3

Configuring Post-Quantum Cryptography

FIPS 140-3 algorithm restrictions