Compare with built-in access control#

Starburst access control and built-in access control are both role-based access control systems for SEP, but they work differently. This page describes the differences and how the two systems work together.

Differences#

Built-in access control

Starburst access control

Where rules live

On each cluster. Clusters share rules only if they share a database.

In the Control Plane, for all clusters that connect to it.

Catalogs

All catalogs on the cluster.

Governed catalogs only.

Access model

Roles. You grant column masks and row filters to roles per table.

Roles, plus attribute-based access control (ABAC) policies for data.

Predefined roles

sysadmin and public.

accountadmin and public.

Users

Not stored. Users are names from your authentication system.

Stored in the Control Plane and managed by your identity provider.

Audit log

Records access to data and changes to access rules.

Doesn’t record access to data. The Control Plane audit log records platform changes, such as creating or deleting clusters and changing access rules.

The two systems use different privilege names, so you can’t copy grants from built-in access control to Starburst access control directly.

Use both systems#

Each catalog in the Control Plane is governed or delegated. Starburst access control controls access to governed catalogs. Delegated catalogs use the other access control systems on the cluster, such as built-in access control or Apache Ranger. A cluster can serve both kinds of catalogs at the same time.

Starburst access control always controls the following, even for delegated catalogs:

  • Roles and role statements, such as SHOW ROLES and SET ROLE

  • Privileges and ownership on catalogs and functions

  • Query management, such as viewing and canceling other users’ queries

  • Reading system information

  • System session properties

  • User impersonation

  • Creating catalogs

  • Catalogs that the cluster doesn’t know about, such as the system catalog

  • Storage locations, when you create a schema or table with an explicit location. Built-in access control location grants don’t apply. For more information, see Privileges.

The two systems have separate roles:

  • A role in one system means nothing to the other, even if the names match.

  • An administrator in one system has no rights in the other. The accountadmin role has no access to delegated catalogs, and the sysadmin role has no access to governed catalogs.

  • In a delegated catalog, users have the privileges of all their built-in access control roles by default. SET ROLE changes only their Starburst access control role. To use one built-in access control role, see Select a built-in access control role.

When users work with both kinds of catalogs, keep the following in mind:

  • A query that uses governed and delegated catalogs needs access in both systems.

  • Starburst access control column masks, row filters, and policies apply only to governed catalogs. Built-in access control masks and filters apply only to delegated catalogs.

  • A SECURITY DEFINER view fails if it reads from a catalog that the other system controls.

  • Starburst access control rules are the same on every cluster. Built-in access control rules depend on each cluster’s access control database.

Grants in SQL#

GRANT, REVOKE, DENY, and SHOW GRANTS statements on a table or view go to the access control system of its catalog:

  • In a governed catalog, the grantee must be a Starburst access control role.

  • In a delegated catalog, the grantee must be a built-in access control role.

Neither system accepts a user as the grantee. GRANT ... ON CATALOG statements always go to Starburst access control, even for delegated catalogs.

Select a built-in access control role#

To use only one of their built-in access control roles in delegated catalogs, users set the $biac-role extra credential in their client. The value is ALL, NONE, or ROLE{name}, and the default is ALL. For example, the following JDBC parameter selects the analyst role:

extraCredentials=$biac-role:ROLE{analyst}

With NONE, users have only the privileges of the public role. Users can select only a role that they already hold, on a cluster that uses the built-in access control database where the role is granted.

You can’t use SET ROLE with a built-in access control role. SET ROLE accepts only Starburst access control roles.

To move catalogs from built-in access control to Starburst access control, see Migrate to Starburst access control.