DATABRICKS UNITY TOKEN
Stores a Databricks personal access token, optionally bound to a metastore.
DATABRICKS UNITY TOKEN is the fifth entry in the Secret Type dropdown and it's available at all three scopes: User, Workspace and Tenant. It carries a Databricks personal access token, the credential Unity Catalog expects when something outside Databricks reads its metadata, and we recognise those tokens by the dapi prefix Databricks issues them with.
This is the type to reach for when you're reading Unity Catalog from Yeedu, which most often happens during a migration where both platforms are running side by side. Binding the optional Metastore dropdown associates the token with a particular metastore registration, so the credential and the catalogue it authenticates against stay together rather than being wired up independently.
Basic Details
Common to every secret type:
| Field | Required | Control | Placeholder / default |
|---|---|---|---|
| Secret Name | Yes | text | title_example_user_secret_1 |
| Secret Type | Yes | dropdown | select DATABRICKS UNITY TOKEN |
| Workspace | Yes | dropdown | Workspace scope only |
| Description | No | textarea | Enter Description |
Secret Details
| Field | Required | Control | Placeholder |
|---|---|---|---|
| Token | Yes | password | e.g., dapi1234567890abcdef1234567890abcdef |
| Metastore | No | dropdown (right column) | Select Metastore |
Validate and Metastore
- Validate is available for this type, and stays disabled until Token is filled.
- This is one of the three types that expose the optional Metastore dropdown. See Secret Validation.
