Connecting to AtScale with TLS enabled

When AtScale is configured in secure mode, all communications between external client applications and the AtScale services must use secure protocols.

You will need to change your BI client connections to use TLS/SSL when talking to AtScale. For example, configure TLS/SSL for your ODBC driver connection, or use HTTPS instead of HTTP when connecting to AtScale Design Center.

This also means that every BI client machine will need any intermediate CA certificates and the root CA certificates needed to build the chain to the root CA. Without these CA certificates, the client machine will not be able to verify the identity of the AtScale server host.

• Supported TLS cipher suites AtScale supports two sets of TLS 1.2 cipher suites: one for the application and one for the engine.