Using SSL Encryption

If your OpenAccess SDK environment requires encryption for data exchanged between the JDBC Client and the OpenAccess SDK Server, you can use the Secure Socket Layer (SSL). OpenAccess SDK supports the use of both anonymous ciphers and cipher suites that support server certificates. However, it should be noted that TLS version 1.3 does not support anonymous cipher suites. The cipher suites supported by TLS version 1.3 and those supported by other protocol versions are mutually exclusive.

The JDBC Client adds a direct encryption mechanism using the encrypted option. For example:

jdbc:openaccess:ssl//mysecurehost:9503;encrypted=1

This type of encryption is directly configured on the OpenAccess SDK Server.

Note: If you want to use cipher suites that support server certificates, you must specify values for Truststore, TruststorePassword, CipherSuites, ValidateServerCertificate, and HostNameInCertificate in the connection string. For example:

jdbc:mysecurehost:ssl://securehost:port;Truststore=keystore.jks;TruststorePassword=secret_keystore;
  CipherSuites=TLS_DHE_DSS_WITH_AES_128_GCM_SHA256;ValidateServerCertificate=true;
  HostNameInCertificate=securehost.xyz.com

For details on configuring SSL for OpenAccess SDK, see Configuring OpenAccess SDK security.