Jump to main content

Support
Academy
DataStax Home

Glossary
Blog
Drivers
Community
Resources
Download Now

DataStax 5.1 Security Guide Earlier DSE version Latest 5.1 patch: 5.1.17

About DSE Advanced Security
Security FAQs
Security checklists
Securing the environment
Configuring DSE Unified Authentication
Connecting to authentication enabled clusters
Managing roles
Authorizing access to database resources
Auditing activity
Transparent data encryption
Configuring SSL

DataStax Astra — Built on Apache Cassandra and designed from the ground up to run anywhere, on any cloud, in any datacenter, and in every possible combination. DataStax delivers the ultimate hybrid and multi-cloud database.

Search other guides

Home
Connecting to authentication enabled clusters
Setting up local or DSE managed JMX user authentication.

Connecting to authentication enabled clusters
Setting up local or DSE managed JMX user authentication.
- About client connections
  After enabling DataStax Unified Authentication provide credentials in connection requests.
- Providing credentials with DSE tools
  Authentication works with any combination of DSE authentication, LDAP pass-through authentication, and Kerberos authentication.
- Providing credentials with nodetool
  Using nodetool with JMX authentication enabled.
- Providing credentials with JConsole
  How to use JConsole with authentication.
- Providing credentials with cqlsh
  Create a cqlshrc file to use credentials when launching a CQL shell session.
- Using dsetool with Kerberos enabled cluster
  Steps to enable dsetool to use Kerberos authentication.
- Using cqlsh with Kerberos or user authentication
  Configuration steps to use cqlsh with DataStax Unified Authentication.
- Loading data into a remote Kerberos enabled cluster
  Configure sstableloader with Kerberos to load data from an sstable into a remote DataStax Enterprise cluster with Kerberos enabled.
- Providing credentials for DSE Graph
  To run DataStax Enterprise Graph with DSE Unified Authentication, configure a user name and password or Kerberos in the Graph remote.yaml.
- Running Spark jobs with Kerberos
  Spark jobs may be run against a Kerberos enabled DataStax Enterprise database.

Connecting to authentication enabled clusters

Setting up local or DSE managed JMX user authentication.

About client connections
After enabling DataStax Unified Authentication provide credentials in connection requests.
Providing credentials with DSE tools
Authentication works with any combination of DSE authentication, LDAP pass-through authentication, and Kerberos authentication.
Providing credentials with nodetool
Using nodetool with JMX authentication enabled.
Providing credentials with JConsole
How to use JConsole with authentication.
Providing credentials with cqlsh
Create a cqlshrc file to use credentials when launching a CQL shell session.
Using dsetool with Kerberos enabled cluster
Steps to enable dsetool to use Kerberos authentication.
Using cqlsh with Kerberos or user authentication
Configuration steps to use cqlsh with DataStax Unified Authentication.
Loading data into a remote Kerberos enabled cluster
Configure sstableloader with Kerberos to load data from an sstable into a remote DataStax Enterprise cluster with Kerberos enabled.
Providing credentials for DSE Graph
To run DataStax Enterprise Graph with DSE Unified Authentication, configure a user name and password or Kerberos in the Graph remote.yaml.
Running Spark jobs with Kerberos
Spark jobs may be run against a Kerberos enabled DataStax Enterprise database.

Contact Us

+1 (650) 389-6000

info@datastax.com

© DataStax | Privacy policy | Terms of use | Updated: 30 March 2020

Build time: 2020-03-30 11:28:24.339

DataStax, Titan, and TitanDB are registered trademark of DataStax, Inc. and its subsidiaries in the United States and/or other countries.

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.

security security51