SSO Configuration

Single Sign-On (SSO) Configuration

The RootCause Platform supports SSO through OIDC and SAMLv2. Configuration is managed in the Helm values.yaml file.

1. Choose a Protocol

Select either OIDC or SAMLv2. Only one should be configured.

2. Configure Secrets

OIDC Example

secrets:
  oidcKeys:
    AUTH_OIDC_ISSUER: "https://auth-test.perceptura.com"
    AUTH_OIDC_CLIENT_ID: "111c04f3-12dc-4933-b933-b4002f8b13c7"
    AUTH_OIDC_CLIENT_SECRET: "RRVWRqmyVrFNUEUbMotsIQ5gl2VzzJQahXwqLLt9iJQ"
    AUTH_OIDC_WELLKNOWN: "https://auth-test.perceptura.com/764ca01d-37fc-4754-abe7-481e63e94b48/.well-known/openid-configuration"
    AUTH_OIDC_LOGOUT_URL: "https://auth-test.perceptura.com/oauth2/logout?client_id=111c04f3-12dc-4933-b933-b4002f8b13c7"

SAMLv2 Example

secrets:
  samlKeys:
    AUTH_SAML_LOGIN_URL: "https://auth-test.perceptura.com/samlv2/login/111c04f3-12dc-4933-b933-b4002f8b13c7"
    AUTH_SAML_LOGOUT_URL: "https://auth-test.perceptura.com/samlv2/logout/111c04f3-12dc-4933-b933-b4002f8b13c7"
    AUTH_SAML_CERTIFICATE: |
      -----BEGIN PUBLIC KEY-----
      -----END PUBLIC KEY-----

3. Set the Protocol

platform:
  env:
    SSO_TYPE: "OIDC"  # or "SAML"

4. Deploy

helm upgrade --install rootcause-platform . -f values.yaml

5. Identity Provider Setup

If using Azure AD, create a new app registration, configure OIDC or SAML, and copy the resulting URLs, client IDs, and secrets into your Helm configuration.