Example 1: SSL-enabled service using a DSA private key and defaultcipher suites

Service for C/C++ Template

A service based on the Service for C/C++ template is configured for server authentication using one of the OpenAccess SDK Clients.

ServiceName=OpenAccessSDK900_C:
ServiceSSLEnabled=1
ServiceSSLKeyStore=C:\Program Files\Progress\DataDirect\oaserver90\cert\MyKeyStore_DSA.p12
ServiceSSLKeyStorePasswordFile=C:\ProgramFiles\Progress\DataDirect\oaserver90\
cert\MyPasswordFile.pw

The cipher suites published by this service are the default cipher suites:

TLS version 1.3

• TLS_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256
• TLS_AES_128_GCM_SHA256

TLS version 1.2

• TLS_DH_anon_WITH_AES_128_CBC_SHA
• TLS_DHE_DSS_WITH_AES_128_CBC_SHA

Service for Java Template

The Java template depends on which TLS version is used.

TLS version 1.3 is supported in JDK 11 and later versions and JDK 8u261 and later versions. The following Cipher suites are supported:

• TLS_AES_256_GCM_SHA384
• TLS_AES_128_GCM_SHA256

ServiceName=OpenAccessSDK900_Java:
ServiceSSLEnabled=1
ServiceSSLKeyStore=C:\Program Files\Progress\DataDirect\oaserver90\cert\MyKeyStore_DSA.p12
ServiceSSLKeyStorePasswordFile=C:\ProgramFiles\Progress\DataDirect\oaserver90\
cert\MyPasswordFile.pw

For TLS version 1.2, the Java service may only be configured to use anonymous ciphers. Because this is the default behavior, you do not need to specify a value for ServiceSSLCipherSuites.

ServiceName=OpenAccessSDK900_Java:
ServiceSSLEnabled=1