For the complete documentation index, see llms.txt. This page is also available as Markdown.

SSO

Configure SAML Single Sign-On (SSO) in Spike for both the incident dashboard and your public status page dashboard.

Spike supports SAML SSO for the incident management dashboard and the status page dashboard. Configure SAML with your Identity Provider (IdP), then paste the XML metadata into Spike to activate SSO.

Set up SAML with your IdP

Guides for common identity providers:

Step 1: Configure SAML in your IdP

Use the values below when configuring SAML. These values apply to Okta, Microsoft Azure AD, Google, and other providers.

Incident management dashboard

  • Assertion consumer service URL / Single Sign-On URL / Destination URL: https://app.spike.sh/sso/oauth/saml

  • Entity ID / Identifier / Audience URI / Audience Restriction: https://app.spike.sh

  • Response: Signed

  • Assertion Signature: Signed

  • Signature Algorithm: RSA-SHA256

  • Assertion Encryption: Unencrypted

Status page dashboard

  • Assertion consumer service URL / Single Sign-On URL / Destination URL: https://statuspage.spike.sh/sso/status-page/oauth/saml

  • Entity ID / Identifier / Audience URI / Audience Restriction: https://statuspage.spike.sh

  • Response: Signed

  • Assertion Signature: Signed

  • Signature Algorithm: RSA-SHA256

  • Assertion Encryption: Unencrypted

SAML configuration example in Okta
Example SAML configuration in Okta.

Step 2: Add user attribute mappings

Add the user attribute mappings as shown below. email, firstName, and lastName are required.

User attribute mappings for SAML SSO

Step 3: Paste the XML metadata in Spike

Open organisation settings, paste the IdP XML metadata, and save.

Paste IdP XML metadata in Spike organisation settings

Step 4: Sign in using your organisation slug

Find your organisation slug in organisation settings and use it at the login screen to sign in via SSO.

Organisation slug in Spike settings

Last updated

Was this helpful?