Integration with Sentry

Arcadia Enterprise integrates with Sentry.

Availability Note. This feature relates to Cloudera installations accessed through Arcadia Engine connections. See Arcadia Connections.

To integrate the Arcadia Visualization server with a Sentry-enabled Hadoop system, you must perform the following tasks:

When you enable a Sentry connection, the system mirrors the roles and group memberships from the Sentry system. This synchronization enables full access to the datasets (and dashboards built on those datasets) to all users with defined Sentry roles and group memberships.

Arcadia stores the group memberships for a roles mirrored from Sentry in a separate sentry_groups field of a role definition. If this field exists, the system does not allow the addition of other users or groups to the role membership. All Sentry role membership must be managed from the Sentry system.

ArcViz mirrors and maintains role definitions from Sentry through periodic polling of the Sentry system, with frequency defined through site settings. If during a polling cycle, the system determines that a role formerly imported from Sentry no longer exists, it empties the sentry groups membership field for that role. This inactivates the role, but preserves the potentially extensive privilege structure assigned to it.

Integration with LDAP

LDAP integration consists of the following steps:

Sentry Integration with LDAP
  1. Users initiate access to the application layer through an SSL-enabled connection protocol.
  2. The system checks user credentials against LDAP. When valid, the user obtains the group membership information, and successfully logs into Arcadia.
  3. The first time the user logs in, Arcadia adds the username in the application metastore. In subsequent user sessions, the system references this user information.
  4. Arcadia establishes domain trust at the Kerberos level, using the service principal account. This account is renewed periodically.
  5. During query execution, Arcadia uses the Kerberos ticket and proxy user privileges to communicate between Arcadia Engine and Arcadia Visualization Server.
  6. The system checks against Sentry, using impersonation for data authorization.
  7. Sentry synchronizes with LDAP users and user groups, and databases.
  8. Arcadia Engine reads HDFS blocks securely, by checking against Sentry.

Integration with RBAC

Arcadia Data's Role Based Access Control framework (RBAC) provides access control over connections and datasets. See Role Based Access Control.

RBAC integrates with existing security systems such as Kerberos/LDAP, Sentry, and Ranger, and takes advantage of other tools for external user and group specification, password management, table- and column-level access, and so on.

Integration with Sentry and/or LDAP enables the following combinations of access control:

Access Control Combinations
Access Control Protocols Users Groups Roles Role-Group Mapping
Sentry and LDAP LDAP, internal LDAP, external Sentry, internal Sentry, internal
Local and LDAP LDAP, internal LDAP, external local local
Local and Sentry local local Sentry, internal Sentry, internal
Local local local local local


  • local: controls provided in the Arcadia Visualization server
  • internal: information from the object in the external system used with objects created in ArcViz
  • external: external objects only mirrored or cached for use by ArcViz

Consider the first case, with both Sentry and LDAP.

  • Users

    The system makes a copy of the user's information to create a user account within ArcViz. It does not store the password, so the account cannot be used without an LDAP connection. Subsequent changes to account information made through the LDAP interface, such as name change, are not picked up by ArcViz.

  • Groups

    The system always references LDAP for group membership definitions.