...

Relational connections can be configured to leverage your enterprise Single Sign-On (SSO) infrastructure for authentication. Additional configuration is required. For more information, see Enable SSO for Relational Connections.

Troubleshooting

Reading or writing over TLS/SSL fails

Reading or writing over TLS/SSL may fail with an error message in the data service data service log similar to the following:

The server selected protocol version TLS11 is not accepted by client preferences [TLS12, SSL20Hello]

In this case:

• External libraries referenced by the data service may use TLS/SSL protocols of their own choosing. 
• These libraries are included during initialization of the data service.
• The listed protocol (TLSv1.1) is a version of the TLS protocol that is no longer supported. 

Solution:

You can configure the platform to override the default protocols supported by Java 8 and to instead use the set of protocols listed in platform configuration. 

1. D s config
   method a

2. When set

...

1. to true, the following parameter instructs the data service to use the protocols listed in Admin Settings page instead. Set this parameter

...

1. to true:

   Code Block
   "data-service.httpsProtocols.reset": false,

   Setting	Description
   false	(default) Supported HTTPS protocols are defined by Java 8.
   true	Supported HTTPS protocols are defined by the D s platform .

2. Locate the following parameter: 

   Code Block
   "data-service.httpsProtocols.defaultProtocols": "SSLv3,TLSv1,TLSv1.1,TLSv1.2"

   Tip
   Tip: You can enter any TLS/SSL protocol supported by Java 8 in the above. Other protocols are likely to cause read/write failures.

3. In this case, you can add the missing protocol to the list, as in the following example:
   
   

   Code Block
   "data-service.httpsProtocols.defaultProtocols": "SSLv3,TLSv1,TLSv1.1,TLSv1.2,TLSv1.1"

4. Save your changes and restart the platform.