Skip to main content

Capabilities

The Databricks connector supports automatic account provisioning and deprovisioning.
Workspace roles (such as workspace-access or databricks-sql-access) can only be granted to users, groups, and service principals that are already members of that workspace. If the request fails because the identity isn’t a member, grant them membership in the workspace first, then request the role again.Revoking the workspace member entitlement removes the principal’s entire workspace assignment. If the principal is also a workspace admin, their admin access to that workspace is removed too. This also applies to groups: revoking the workspace member entitlement from a group removes the group’s entire workspace assignment, including admin access if the group is a workspace admin (its members lose it).
This connector syncs non-human identities and displays them on the Identities overview dashboard.

Connector actions

Connector actions are custom capabilities that extend C1 automations with app-specific operations.
These actions act on the account-level user, so disabling a user blocks them in the Databricks account and in every workspace. Only the user’s active status changes: their permissions and memberships are kept, so enabling the user restores the same access. Running an action on a user who is already in the target state succeeds. Account provisioning doesn’t reactivate an inactive user; run enable_user instead.

Authentication methods

The connector authenticates with OAuth — an account-level service principal’s client ID and secret. This is the only authentication method the connector supports.

Gather Databricks credentials

Configuring the connector requires you to pass in credentials generated in Databricks. Gather these credentials before you move on.
A user with the Account admin role in each Databricks workspace you want to sync must perform this task.

Look up your Databricks account ID

1
Ensure that your Databricks user account has the Account admin role and is assigned to each Databricks workspace you want to sync to C1.
2
In the Databricks account console, open the menu that appears next to your username in the upper right corner.
3
Carefully and copy and save account ID.

Generate Databricks credentials

The Databricks connector authenticates with OAuth, which syncs info from all Databricks workspaces the service principal can access.
1
Follow the Databricks OAuth authentication documentation to create a service principal and create an OAuth secret.
2
Carefully copy and save the OAuth client ID and secret.
Done. Here’s the set of credentials you’ll need when setting up the connector:
  • Account ID
  • OAuth client ID
  • OAuth client secret
Next, move on to the instructions for your chosen setup method.

Configure the Databricks connector

To complete this task, you’ll need:
  • The Connector Administrator or Super Administrator role in C1
  • Access to the set of Databricks credentials generated by following the instructions above
Follow these instructions to use a built-in, no-code connector hosted by C1.
1
In C1, navigate to Apps > Connectors and click Add connector.
2
Search for Databricks and click Add.
3
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
4
Set the connector’s Name and, optionally, a Description.
5
Click the pencil icon next to Owners to choose who can configure and manage this connector.
6
Click Add. The connector is created and its configuration page opens.
7
Find the Settings area of the page and click Edit.
8
Paste the account ID you looked up in Step 1 into the Account ID field.
9
Enter your OAuth client ID and client secret into the OAuth2 Client ID and OAuth2 Client Secret fields.
10
Google Cloud Platform and Azure Databricks customers only: Enter your Databricks account hostname and hostname in the relevant fields.
11
Click Save.
12
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
Done. Your Databricks connector is now pulling access data into C1.