Secure connections from DataStax Studio to DataStax Enterprise

DataStax Studio is composed of a web browser client and a Studio server. Security for DataStax Studio includes protecting the browser client-to-Studio server component, and the Studio server-to-database component.

A connection from each notebook to a cluster is required. Connect notebooks only to clusters that run the relevant workload. See Create a connection in DataStax Studio.

Secure connections between DataStax Studio and DataStax Enterprise (DSE) using SSL client-to-node encryption or internal/LDAP authentication. DataStax recommends securing ports in compliance with your security policy.

SSL client-to-node encryption

Client-to-node encryption protects in-flight data from client machines to a database cluster using SSL (Secure Sockets Layer) and establishes a secure channel between the client and the coordinator node. SSL must be configured and working on your DSE cluster. To use SSL to connect Studio to an SSL-enabled DataStax Enterprise cluster, see Use SSL connections in DataStax Studio.

Internal and LDAP authentication

Internal or LDAP authentication must be configured on the DSE server. To enable internal username-password authentication for the connection from DataStax Studio to DSE, set the authenticated username and password in DataStax Studio when Creating a connection in DataStax Studio.

Changing the httpBindAddress setting from the default (localhost) can pose a security risk, allowing users on external machines to gain access to Studio notebooks and the data in the DSE clusters to which those notebooks are connected. Studio is designed to be used as a desktop application. Distributed deployment introduces potential security risks.

Secure connections from DataStax Studio to DataStax Enterprise

SSL client-to-node encryption

Internal and LDAP authentication

Was this helpful?

Give Feedback