SigNoz
Docs
PricingCustomers
Get Started - Free
Docs
IntroductionContributingMigrate from DatadogSigNoz API
OpenTelemetry
What is OpenTelemetryOpenTelemetry Collector GuideOpenTelemetry Demo
Community
Support
Slack
X
Launch Week
Changelog
Dashboard Templates
DevOps Wordle
Newsletter
KubeCon, Atlanta 2025
More
SigNoz vs DatadogSigNoz vs New RelicSigNoz vs GrafanaSigNoz vs Dynatrace
Careers
AboutTermsPrivacySecurity & Compliance
SigNoz Logo
SigNoz
All systems operational
HIPAASOC-2
SigNoz Cloud - This page applies to SigNoz Cloud editions.
Self-Host - This page applies to self-hosted SigNoz editions.

Single Sign on (SSO) - Overview

SigNoz supports single sign-on (SSO), allowing users to authenticate through an external identity provider (IdP) instead of maintaining SigNoz-specific passwords.

What’s supported

  • SAML 2.0: Available on SigNoz Cloud and Enterprise Self-Hosted
  • OIDC: Available on SigNoz Cloud and Enterprise Self-Hosted
  • Google Workspace (OAuth2): Available on Community Edition, SigNoz Cloud and Enterprise Self-Hosted

How SSO works in SigNoz

At a high level, you connect your organization’s email domain to an IdP, and SigNoz defers authentication to that IdP.

  1. Authenticated Domain: You register a domain like example.com under Settings → Organization Settings → Authenticated Domains.
  2. Choose Method: For that domain, select SAML, OIDC, or Google (for Workspace) and provide the IdP details.
  3. Just‑in‑Time access: Users with emails on that domain can sign in via your IdP without a prior invite.
  4. Attribute/Claim Mapping: Map IdP attributes (SAML) or token claims (OIDC/Google) to SigNoz user fields like email, display name, groups, and role.
  5. Role Mapping: Automatically assign SigNoz roles (VIEWER, EDITOR, ADMIN) based on IdP group memberships or a direct role attribute — no manual role assignment needed.

Setup at a glance

  • Go to Settings → Organization Settings → Authenticated Domains
  • Add your organization’s email domain (e.g., example.com)
  • Click Configure SSO and choose a method
  • Save and test from an incognito window
  • Optionally toggle Enforce SSO for that domain
  • If you encounter any issues, you can temporarily use password authentication by appending ?password=Y to the login URL, e.g. <your-instance-url>/login?password=Y.

IdP‑Initiated SSO setup

If your provider supports IdP-initiated logins, you will see an option to set the Relay State URL in the IdP's configuration UI.

  • Copy the IdP Initiated SSO URL from the Authenticated Domains section and set this as the Relay State URL in your IdP

Next steps

Looking for step-by-step setup? See the user guides below:

  • Google Workspace
  • SAML with Microsoft Entra ID
  • SAML with Okta
  • SAML with AWS IAM Identity Center (AWS SSO)
  • SAML with JumpCloud
  • SAML with Keycloak
  • OIDC with Keycloak

Last updated: February 26, 2026

Edit on GitHub

Was this page helpful?

Your response helps us improve this page.

Prev
Serving on an External URL
Next
JumpCloud - SAML Authentication
On this page
What’s supported
How SSO works in SigNoz
Setup at a glance
IdP‑Initiated SSO setup
Next steps

Is this page helpful?

Your response helps us improve this page.