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
  • SSO
  • Supported Identity Providers
  • Planned Identity Providers
  1. Pipekit

Authentication

Last updated 3 days ago

When you first sign up to Pipekit, you can choose to authenticate using various social providers, with your email address or a username and password combination.

SSO

After creating your Pipekit account, you have the option of converting your Pipekit Organization to use SSO. This will allow members of your organization to authenticate with your chosen Identity Provider (IdP).

Supported Identity Providers

Planned Identity Providers

  • Google Workspace

  • Microsoft Entra ID

Okta