Sleuth Documentation
HomeBlogSupportSign up
  • Getting started
  • Navigating Sleuth
  • DORA metrics
    • Deploy frequency
    • Change lead time
    • Change failure rate
    • MTTR
    • Interpreting Metrics in Sleuth
  • Deployment tracking
    • Organization
      • Labels
      • Trends
      • Compare
      • Search
      • Status
    • Projects
      • Issue trackers
    • Environments
    • Code deployments
      • Creating a deployment
      • How to register a deploy
      • Rollbacks
      • Automatic tagging
      • Deployment locking
      • Environment drift
      • Move code deployments
      • Search everything
    • Feature flags
    • Manual changes
    • Deploys
    • Teams
  • Work in Progress
  • Goals
  • Sleuth Automations
    • Automations Marketplace
      • Installing Automations
        • Installing PR "Update" Automations
      • Editing and uninstalling Automations
      • Smart suggestions
      • Understanding efficacy
    • Custom Automations
      • Automations Cookbook
      • Webhook Actions
      • Trigger Build Actions
        • Bitbucket Pipelines
        • CircleCI
        • Github Actions
        • Jenkins
  • Slack & Email Notifications
  • Auto-verify deploys
    • Anomaly detection
    • Error impact
    • Metric impact
  • Ignoring pull requests
  • Slack mission control
    • Approvals
    • Project notifications
    • Personal notifications
    • Search Sleuth in Slack
    • Project/Deployment history
    • Developer standup
  • Sleuth API
    • Deploy Registration
    • Deploy import
    • Manual Change
    • Custom Incident Impact Registration
    • Custom Metric Impact Registration
    • Deprecation information
    • GraphQL Queries
    • GraphQL Mutations
    • Query batching
  • Integrations
    • About Integrations...
    • Code integrations (read-only)
      • Azure DevOps
      • Bitbucket
      • GitHub
      • GitLab
      • Custom Git
      • Terraform Cloud
    • Code integrations (write)
    • Feature flag integrations
      • LaunchDarkly
    • Impact integrations
      • Error trackers
        • Bugsnag
        • Honeybadger
        • Rollbar
        • Sentry
      • Metric trackers
        • AppDynamics
        • AWS CloudWatch
        • Custom
        • Datadog
        • Jira metrics (Cloud / Data Center)
        • NewRelic
        • SignalFx
      • Incident tracker integrations
        • Blameless
        • PagerDuty
        • Datadog Monitors
        • Statuspage
        • Opsgenie
        • Jira (Cloud/Data Center)
        • FireHydrant
        • Rootly
        • ServiceNow
        • Custom
          • Grafana OnCall
      • CI/CD builds
        • Azure Pipelines
        • Bitbucket Pipelines
        • Buildkite
        • CircleCI
        • GitHub Actions
        • GitLab CI/CD Pipelines
        • Jenkins
    • Sleuth DORA App for Slack
    • Microsoft Teams integration
    • CI/CD integrations
      • Azure Pipelines
      • Bitbucket Pipelines
      • Buildkite
      • CircleCI
      • Github Actions
      • GitLab CI/CD Pipelines
      • Jenkins
    • Issue tracker integrations
      • Jira Cloud
      • Jira Data Center
      • Linear
      • Shortcut
    • Fixing broken integrations
  • Pulse
    • Welcome to Pulse docs
    • Quick Start setup guide
    • Beginner tutorials
      • 1. How to create a Teamspace
      • 2. How to create a Review
      • 3. How to create a Survey
  • Features
    • Reviews
      • Review workflow
      • Review templates
      • Widgets and Sections
        • Widget type
      • Review settings
    • Surveys
      • Survey Workflow
    • Teamspaces
    • Inbox
    • AI assistant
    • General settings
      • Users and Teams
      • Investment mix
  • Settings
    • Organization settings
      • Details
      • Authentication
        • SAML 2.0 Setup
          • Okta Configuration
          • Azure AD Configuration
          • PingIdentity Configuration
      • Access Tokens
      • Members
      • Team Settings
      • Billing
    • Project settings
      • Details
      • Slack settings
      • Environment settings
      • Code deployment settings
      • Feature flag settings
      • Impact settings
    • Account settings
      • Account settings
      • Notifications settings
      • Identities settings
    • Role Based Access Control
  • Resources
    • FAQ
    • Sleuth TV
    • Purchasing
    • About Sleuth...
Powered by GitBook
On this page
  • Gather Sleuth Service Provider Metadata
  • Establish Sleuth as a trusted Service Provider
  • Enter IdP metadata into Sleuth
  • Enable SAML login

Was this helpful?

  1. Settings
  2. Organization settings
  3. Authentication

SAML 2.0 Setup

PreviousAuthenticationNextOkta Configuration

Last updated 1 year ago

Was this helpful?

To set up SAML integration you will need admin privileges in Sleuth and in your Identity Provider (IdP) system that supports SAML 2.0. Regardless of the specific IdP, the general setup process is roughly the same:

  1. This is the information you will need in order for your IdP to identify Sleuth as a trusted service provider.

  2. This step requires administrator privileges in your IdP.

  3. Finalize communication configuration between Sleuth and IdP

To begin SAML configuration navigate to the "Authentication" tab under "Organization settings" and click "Configure SAML Authentication":

Gather Sleuth Service Provider Metadata

To view the Sleuth SAML metadata expand the "Sleuth Service Provider data" section by clicking on the title.

Once expanded, you can either download the metadata XML file (if your IdP supports metadata file imports) or manually copy-paste these values when setting up Sleuth as a trusted service provider within your IdP.

Establish Sleuth as a trusted Service Provider

To establish Sleuth as a trusted SP you will need information from the previous step and administrator privileges in your IdP.

This section includes instructions on how to configure your Identity Provider in order to enable the login:

Even if your Identity Provider is not specified in the list above, Sleuth is respecting the SAML 2.0 standard so you can integrate every Identity Provider that supports the standard.

Enter IdP metadata into Sleuth

To enter your IdP's metadata into Sleuth you will need information from the previous steps and administrator privileges in Sleuth.

This section includes instructions on how to configure Sleuth in order to enable the login with your selected IdP:

Even if your Identity Provider is not specified on the list above, Sleuth is respecting the SAML 2.0 standard so you can integrate any Identity Provider that supports the standard.

Enable SAML login

  1. Log out of Sleuth.

  2. On the login page: enter your email and click "Continue".

  3. Clicking on "SAML" will start the login process via your IdP.

Feel free to contact us at in case of any problems setting up the integration.

Feel free to contact us at in case of any problems setting up the integration.

Once you saved the configuration you will need to successfully log in using SAML before you can set it to be your only .

Okta
Azure AD
support@sleuth.io
support@sleuth.io
Gather Sleuth Service Provider (SP) Metadata.
Establish Sleuth as a trusted SP in your IdP.
Enter IdP metadata into Sleuth.
Enable SAML login for users.
Azure AD
allowed login method
Okta