How to Specify Native/ASO Encryption From Within a JDBC Connect String
(Doc ID 2756154.1)
Last updated on MARCH 14, 2023
Applies to:JDBC - Version 19.3 and later
Information in this document applies to any platform.
Starting with Oracle Release 19c, all JDBC properties can be specified within the JDBC URL/connect string. This is documented in the 19c JDBC Developer's Guide here.
The is done via name-value pairs. A question mark (?) indicates the beginning of any name-value pairs. For example:
If multiple name-value pairs are used, an ampersand (&) is used as a delimiter between them.
The following example illustrates how this functionality can be utilized to specify native/Advanced Security (ASO) encryption from within the connect string.
Note that, when using native/ASO encryption, both the Oracle database and the JDBC driver default to "ACCEPTED". This means that no settings are needed in the database SQLNET.ORA file in the below example; if the client specifies "REQUIRED", then encryption will take place. A table that shows the possible combination of client-side and server-side settings can be found in the 19c JDBC Developer's Guide here.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document