Configure authentication to Glean

Important

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Azure Databricks previews.

This page shows how to configure Glean to enable authentication from Azure Databricks for the Glean connector. Use the credentials retrieved from the steps on this page to create a Unity Catalog connection in Azure Databricks.

Prerequisites

• A Glean deployment with the Client API. The connector reads insights and shortcuts through the Glean Client API.
• Admin access to create a Glean Client API token. Super Admins can create tokens for any user; Admins and API Token Creators can create tokens for themselves. See Glean-issued tokens.
• Your Glean deployment subdomain. If your Glean instance is at https://mycompany.glean.com, the subdomain is mycompany, and the Client API base URL is https://mycompany-be.glean.com.

Configure Glean

The Glean connector authenticates with a Glean Client API token, sent as an HTTP Bearer token. The token must carry both the INSIGHTS and SHORTCUTS scopes so that the connector can ingest both source tables. For more information, see the Glean-issued token reference.

Create a Client API token

1. In Glean, go to Client API Token Settings.
2. Select Add New Token.
3. Enter a Description to identify the token.
4. Under Scopes, select both INSIGHTS and SHORTCUTS.
5. (Optional) Set an Expires date. Databricks recommends setting an expiration and rotating the token regularly.
6. Select Save Token Securely, then copy the token. Glean shows the token secret only once. Store it securely and use it as the API Token on the connection page.

Note

Token scopes can't be changed after creation. If you need to add a scope later, create a new token with both scopes.

Next steps

Create a Glean connection in Azure Databricks. See Create a Glean connection.