• Glossary
  • Support
  • Downloads
  • DataStax Home
Get Live Help
Expand All
Collapse All

DataStax Enterprise 6.8 Security Guide

    • About DSE Advanced Security
    • Security FAQs
    • Security checklists
    • Securing the environment
      • Securing ports
      • Securing the TMP directory
    • Authentication and authorization
      • Configuring authentication and authorization
        • About DSE Unified Authentication
          • Steps for new deployment
          • Steps for production environments
        • Configuring security keyspaces
        • Setting up Kerberos
          • Kerberos guidelines
          • Enabling JCE Unlimited
            • Removing AES-256
          • Preparing DSE nodes for Kerberos
            • DNS and NTP
            • krb5.conf
            • Principal
            • Keytab
        • Enabling authentication and authorization
          • Defining a Kerberos scheme
          • Defining an LDAP scheme
        • Configuring JMX authentication
        • Configuring cache settings
        • Securing schema information
      • Managing database access
        • About RBAC
        • Setting up logins and users
          • Adding a superuser login
          • Adding database users
          • LDAP users and groups
            • LDAP logins
            • LDAP groups
          • Kerberos principal logins
          • Setting up roles for applications
          • Binding a role to an authentication scheme
        • Assigning permissions
          • Database object permissions
            • Data resources
            • Functions and aggregate resources
            • Search indexes
            • Roles
            • Proxy login and execute
            • Authentication schemes
            • DSE Utilities (MBeans)
            • Analytic applications
            • Remote procedure calls
          • Separation of duties
          • Keyspaces and tables
          • Row Level Access Control (RLAC)
          • Search index permissions
          • DataStax Graph keyspace
          • Spark application permissions
          • DataStax Studio permissions
          • Remote procedure calls
          • DSE client-tool spark
          • JMX MBean permissions
          • Deny (denylist) db object permission
          • Restricting access to data
      • Providing credentials from DSE tools
        • About clients
        • Internal and LDAP authentication
          • Command line
          • File
          • Environment variables
          • Using CQLSH
        • Kerberos
          • JAAS configuration file location
          • Keytab
          • Ticket Cache
          • Spark jobs
          • SSTableLoader
          • Graph and gremlin-console
          • dsetool
          • CQLSH
        • Nodetool
        • JConsole
    • Auditing database activity
      • Enabling database auditing
      • Capturing DSE Search HTTP requests
      • Log formats
      • View events from DSE audit table
    • Transparent data encryption
      • About Transparent Data Encryption
      • Configuring local encryption
        • Setting up local encryption keys
        • Encrypting configuration file properties
        • Encrypting system resources
        • Encrypting tables
        • Rekeying existing data
        • Using tools with TDE-encrypted SSTables
        • Troubleshooting encryption key errors
      • Configuring KMIP encryption
      • Encrypting Search indexes
        • Encrypting new Search indexes
        • Encrypting existing Search indexes
        • Tuning encrypted Search indexes
      • Migrating encrypted tables from earlier versions
      • Bulk loading data between TDE-enabled clusters
    • Configuring SSL
      • Steps for configuring SSL
      • Creating SSL certificates, keystores, and truststores
        • Remote keystore provider
        • Local keystore files
      • Securing node-to-node connections
      • Securing client-to-node connections
        • Configuring JMX on the server side
        • nodetool, nodesync, dsetool, and Advanced Replication
        • JConsole (JMX)
        • SSTableloader
        • Connecting to SSL-enabled nodes using cqlsh
      • Enabling SSL encryption for DSEFS
      • Reference: SSL instruction variables
    • Securing Spark connections
  • DataStax Enterprise 6.8 Security Guide
  • Authentication and authorization
  • Managing database access
  • Assigning permissions
  • Spark application permissions

Setting up DSE Spark Application Permissions

Manage user access to Spark applications. The CQL resources for Spark applications are WORKPOOL and SUBMISSION. Create permissions on the workpool resource controls the ability of a user to submit a Spark application to DSE. Modify permissions on submission resource controls the ability of a user to manage and remove applications.

Procedure

  • Use CQL shell (cqlsh) to authorize access to DSE Resource Manager and Spark applications. All commands must be entered on a DSE Analytics node in the cluster.

  • Access required for AlwaysOn SQL roles:

    GRANT ALL PERMISSIONS ON REMOTE OBJECT AlwaysOnSqlRoutingRPC to <role_name>;
    GRANT ALL PERMISSIONS ON REMOTE OBJECT DseResourceManager TO <role_name>;
    GRANT ALL PERMISSIONS ON REMOTE OBJECT DseClientTool TO <role_name>;
    GRANT SELECT, MODIFY ON dse_analytics.alwayson_sql_cache_table TO <role_name>;
    GRANT SELECT, MODIFY ON dse_analytics.alwayson_sql_info TO <role_name>;
  • Access to only DSE Resource Manager:

    GRANT EXECUTE ON REMOTE OBJECT DseResourceManager TO <role_name>;
  • Run applications:

    GRANT EXECUTE ON REMOTE OBJECT DseClientTool TO <role_name>

    Each DSE Analytics user must have permission to make remote procedure calls with DSE client tools.

  • For roles that are not superusers, access to the following tables is required:

    GRANT SELECT ON system.size_estimates TO <role_name>;
    GRANT SELECT, MODIFY ON "HiveMetaStore".sparkmetastore TO <role_name>;

    Additional permissions are required when running AlwaysOn SQL:

    GRANT SELECT, MODIFY ON dse_analytics.alwayson_sql_cache_table TO <role_name>;
  • Submit applications:

    • To all datacenters:

      GRANT CREATE ON ANY WORKPOOL TO <role_name>;

      Use revoke command to remove access:

      REVOKE CREATE ON ANY WORKPOOL FROM <role_name>;
    • A particular datacenter:

      GRANT CREATE ON WORKPOOL <datacenter_name> TO <role_name>;

      Use revoke command to remove access:

      REVOKE CREATE ON WORKPOOL <datacenter_name> FROM <role_name>;

    The role used to submit an application is automatically granted permission to MODIFY the application.

  • Modify applications:

    • All applications:

      GRANT MODIFY ON ANY SUBMISSION TO <role_name>;

      Use revoke command to remove access:

      REVOKE MODIFY ON ANY SUBMISSION FROM <role_name>;
    • All applications in a particular datacenter:

      GRANT MODIFY ON ANY SUBMISSION IN WORKPOOL '<datacenter_name>.*' TO <role_name>;

      Use revoke command to remove access:

      REVOKE MODIFY ON ANY SUBMISSION IN WORKPOOL '<datacenter_name>.*' FROM <role_name>;

      You must specify a workpool name or wildcard when specifying a datacenter. In DSE versions prior to 6.0, you could specify the datacenter name only, but omitting the workpool name or wildcard results in a syntax error.

    • Specific application in a particular datacenter:

      GRANT MODIFY ON SUBMISSION <id> IN WORKPOOL '<datacenter_name>.*' TO <role_name>;

      Use revoke command to remove access:

      REVOKE MODIFY ON SUBMISSION <id> IN WORKPOOL '<datacenter_name>.*' FROM <role_name>;

      For example, to revoke the MODIFY permissions of an application started by a role named sparkrole, first find the application ID:

      LIST ALL PERMISSIONS OF sparkrole;
      role      | username  | resource
      ----------+-----------+-----------------------------------------------------------
      ...
      sparkrole | sparkrole | <submission app-20190519161729-0004 in work pool default in Analytics>
      sparkrole | sparkrole | <submission app-20190519161729-0004 in work pool default in Analytics>
      sparkrole | sparkrole | <submission app-20190519161729-0004 in work pool default in Analytics>
      ...
      | permission | granted | restricted | grantable
      +------------+---------+------------+-----------
      ...
      |     MODIFY |    True |      False |     False
      |  AUTHORIZE |    True |      False |     False
      |   DESCRIBE |    True |      False |     False
      ...

      In the resource column the application ID follows submission. Here, the application ID is app-20190519161729-0004.

      Use the REVOKE command, specifying the role name, datacenter, and workpool listed in the resource column in the previous command.

      REVOKE MODIFY ON SUBMISSION 'app-20190519161729-0004' IN WORKPOOL 'Analytics.default' FROM sparkrole;

      To revoke all permissions from the application, use REVOKE ALL:

      REVOKE ALL ON SUBMISSION 'app-20190519161729-0004' IN WORKPOOL 'Analytics.default' FROM sparkrole;

      You must specify a workpool name or wildcard when specifying a datacenter. In DSE versions prior to 6.0, you could specify the datacenter name only, but omitting the workpool name or wildcard results in a syntax error.

      GRANT EXECUTE ON REMOTE OBJECT DseGraphRpc TO <role_name>;

Example

Create role for AlwaysOn SQL (alwayson_sql):

CREATE ROLE alwayson_sql WITH LOGIN=true; // role name matches auth_user

// Required if scheme_permissions true
GRANT EXECUTE ON ALL AUTHENTICATION SCHEMES TO alwayson_sql;

// Spark RPC settings
GRANT ALL PERMISSIONS ON REMOTE OBJECT DseResourceManager TO alwayson_sql;
GRANT ALL PERMISSIONS ON REMOTE OBJECT DseClientTool TO alwayson_sql;
GRANT ALL PERMISSIONS ON REMOTE OBJECT AlwaysOnSqlRoutingRPC to alwayson_sql;
GRANT ALL PERMISSIONS ON REMOTE OBJECT AlwaysOnSqlNonRoutingRPC to alwayson_sql;

// Spark and DSE required table access
GRANT SELECT ON system.size_estimates TO alwayson_sql;
GRANT SELECT, UPDATE, TRUNCATE ON "HiveMetaStore".sparkmetastore TO alwayson_sql;
GRANT SELECT, UPDATE, TRUNCATE ON dse_analytics.alwayson_sql_cache_table TO alwayson_sql;
GRANT SELECT, UPDATE, TRUNCATE ON dse_analytics.alwayson_sql_info TO alwayson_sql;

// Permissions to create and change applications
GRANT CREATE, DESCRIBE ON ANY WORKPOOL TO alwayson_sql;
GRANT UPDATE, TRUNCATE, DESCRIBE ON ANY SUBMISSION TO alwayson_sql;
DataStax Graph keyspace DataStax Studio permissions

General Inquiries: +1 (650) 389-6000 info@datastax.com

© DataStax | Privacy policy | Terms of use

DataStax, Titan, and TitanDB are registered trademarks 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 Pulsar, Pulsar, 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.

Kubernetes is the registered trademark of the Linux Foundation.

landing_page landingpage