LogoLogo
PipekitPricingBlogPipekit StatusRelease Notes
  • Introduction
  • Getting Started
  • CLI
    • Cron Workflows
  • Pipekit Agent
    • Helm Install
  • Pipekit
    • Authentication
      • Okta
    • Runs
    • Pipes
      • Managing Pipes
        • Run Conditions
        • Secrets
        • Alerting
      • Pipe Runs
        • Run Graph (DAG)
        • Pod Logs
        • Workflow Logs
        • Workflow YAML
      • Cron Workflows
      • Externally Triggered Workflows
    • Metrics
    • Templates
    • Clusters
    • Organization
      • Creating an Organization
      • Managing Users
      • Managing Alert Providers
      • Settings
      • Permissions
  • Python SDK
    • Jupyter Notebooks
    • Python Scripts
  • Self-Hosting Pipekit
    • Dependencies and Pre-requisites
    • Container Images
    • Kubernetes Permissions
    • Self-Hosted Pipekit Helm Chart
    • License Key
    • Initial Login and Break Glass Account
    • Integrating with your Git Provider
    • Configuring SSO
  • Additional Information
    • Free Trial Cluster
  • REST API
Powered by GitBook
On this page
  • GitLab
  • Microsoft (Azure AD/Entra)
  1. Self-Hosting Pipekit

Configuring SSO

Last updated 9 months ago

These examples assume you are self-hosting Pipekit on the subdomain pipekit.example.com. Replace this with your actual domain.

GitLab

  1. Go to your GitLab group settings and click on "Applications"

  2. Click on "New Application"

  3. Fill in the details:

    • Name: [Choose a unique App name]

    • Redirect URI:

    • Tick "Confidential"

    • Scopes:

      • read_user

      • openid

      • profile

      • email

  4. Click "Save application"

  5. Note down the Application ID and Secret and pass them to the to configure Pipekit.

Microsoft (Azure AD/Entra)

  1. Create a new app registration in your Azure AD tenant.

  2. Fill in the details:

    • Name: [Choose a unique App name]

    • Supported account types: Choose the account types you want to support.

    • Redirect URI:

      • Platform: Web

  3. After creating the app, create a Client Secret and note it down.

  4. Then add the following API permissions:

    • Microsoft Graph:

      • email

      • openid

      • profile

      • User.Read

Note the Application (client) ID and pass it along with the Client Secret to the to configure Pipekit.

https://pipekit.example.com/api/id/v1/sso/gitlab/callback
Helm Chart Values
https://pipekit.example.com/api/id/v1/sso/microsoft/callback
Helm Chart Values