Skip to main content
Last updated on

Configure authentication to GitLab

Beta

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for GitLab from the Previews page. See Manage Databricks previews.

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

Prerequisites​

  • You must be able to create a GitLab OAuth application that you own on gitlab.com. The connector ingests from gitlab.com, not from self-managed GitLab instances.
  • The authenticating user must be a member of the groups and projects you want to ingest. The connector reads only the groups and projects that user can access.
  • Some tables require a paid GitLab tier. See Which GitLab plans does the connector require?.
  • You need your Databricks workspace domain to set the OAuth application's redirect URI.

Configure GitLab​

Register a GitLab OAuth application to obtain the client credentials that Databricks uses to authenticate. See the GitLab OAuth provider documentation.

  1. Sign in to gitlab.com and select your avatar in the upper-right corner.
  2. Select Edit profile.
  3. In the left sidebar, select Access > Applications.
  4. Select Add new application.
  5. In Name, enter a name for the application.
  6. In Redirect URI, enter https://<your-workspace-domain>/login/oauth/http.html.
  7. Under Scopes, select read_api. This scope grants read access to the API across the groups and projects the authenticating user can access.
  8. Select Save application.
  9. Copy the Application ID. Copy the Secret by selecting Copy in the Secret field. You enter these when you create the connection.

Next steps​

Create a GitLab connection in Databricks. See Create a GitLab connection.

On this page