Search the documentation
Search the documentation...
SplitSecure documentation

On this page

Procedure · 9 steps

PagerDuty

Sign in to PagerDuty through SplitSecure, so each sign-in waits for your Guardian Team to approve it.

Updated

Before you start

  • Account Owner access to PagerDuty, on a plan that includes SSO (single sign-on).
  • Your PagerDuty subdomain: for https://acme.pagerduty.com, it is acme.
  • A SplitSecure identity provider, created in a threshold vault and approved by its Guardian Team. See Create an identity provider.

  • A second browser profile, signed in to the Web App, for the test sign-in. Start and finish the test in that same profile.

This guide makes PagerDuty a connected app of your SplitSecure identity provider, so a user signs in to PagerDuty only when your Guardian Team, the group of devices that together approve each proposal, approves it. You collect the identity provider’s values in the Web App, point PagerDuty’s SAML settings at them, then create the matching connected app from PagerDuty’s metadata.

Values you exchange

Value Where to find it Where to paste it
Signing certificate (PEM) The identity provider’s SAML endpoints card, Download Certificate → PEM format PagerDuty, X.509 Certificate, in Point PagerDuty at SplitSecure
SSO URL (HTTP-Post) The same card PagerDuty, Login URL, in the same step
PagerDuty metadata (XML) https://<subdomain>.pagerduty.com/sso/saml/metadata, in Download the PagerDuty metadata The Web App, Metadata File, in Create the connected app

Collect the SplitSecure values

In the Web App

In the Web App, open Vaults, then your vault, then the identity provider. The SAML endpoints card shows three values:

  • SAML IdP Entity ID
  • SSO URL (HTTP-Redirect)
  • SSO URL (HTTP-Post)

Under them, Download metadata XML saves the metadata file and Download Certificate offers the certificate in PEM format or DER format.

  1. Click Download Certificate → PEM format and save the file.
  2. Copy the SSO URL (HTTP-Post).

Configure SSO in PagerDuty

In PagerDuty

  1. Sign in to https://<subdomain>.pagerduty.com.
  2. Go to Settings → Single Sign-On.
  1. Under Login Authentication, select SAML.

  2. Fill in the fields.

    Field Value
    X.509 Certificate The certificate’s full textFrom Download Certificate → PEM format on the card. Paste everything, -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines included
    Login URL The SSO URL (HTTP-Post)From the SAML endpoints card, not the SSO URL (HTTP-Redirect)
  3. Set the authentication options.

    Option Value
    Allow username/password login On while you test, off afterSee Turn off password sign-in below
    Require EXACT authentication context comparison On
    Require signed authentication requests OnPagerDuty signs each request it sends to SplitSecure

Pick one option.

Option Effect
Auto-provision users on first login PagerDuty creates the user at the first sign-in, from the Name, Role and Job Responsibilities the connected app sends
Redirect non-provisioned users PagerDuty sends an unknown user to the Destination Link you enter, for example an internal wiki page
Neither You create each user under People → Users → Add Users before the first sign-in

Click Save Changes. PagerDuty can take a few minutes to apply the change.

Open https://<subdomain>.pagerduty.com/sso/saml/metadata with your subdomain and save the XML file. You upload it to the Web App in the next step.

Connect PagerDuty to SplitSecure

In the Web App

In the Web App, open Vaults, then your vault, then the identity provider. Click New Connected App and pick the service provider’s card. Name is required, and the Threshold Identity Provider field is fixed to this provider.

  1. Click the PagerDuty (SAML2) card.

  2. Enter a Name, for example PagerDuty.

  3. Set the NameID. PagerDuty matches each user by the email in the NameID, so the email SplitSecure sends must equal the user’s PagerDuty login email. The NameID format is fixed to Email Address.

    Keep the default NameID value, Built from each person’s email. Its NameID template is ${user.email}, which SplitSecure fills with the email of the person who signs in. To accept only one email domain, enter it in Email must end with, for example @example.com. SplitSecure then refuses anyone whose email ends otherwise.

  4. Under Metadata File, upload the XML file from Download the PagerDuty metadata.

  5. Under Auto-provisioning attributes, set the values for new PagerDuty users. All three are optional. PagerDuty applies them only when it creates a user at first sign-in, with “Auto-provision users on first login” turned on. Every user it creates through this app gets the same values. Later sign-ins do not change existing users.

    Field Value
    Name A display nameEvery user created through this app gets this name. Leave it empty if several people sign in through this app. PagerDuty then uses each person’s email
    Role A role from the list, or NoneEvery user created through this app gets this role. With None, PagerDuty gives the Manager role (user). Observer needs PagerDuty Advanced Permissions. See the values in PagerDuty’s Optional Attributes for Auto-Provisioning (opens in a new tab)
    Job Responsibilities The user’s job title or responsibilitiesEvery user created through this app gets this value
  6. Optionally, under Advanced Options, turn on Selective notifications so members can choose who gets notified for the Guardian Team’s proposals, set the Account Sensitivity banner shown on this connected app’s proposals (None, Low, Medium, High or Critical), and enter a Description or a Reason for creation.

  7. Click Propose connected app. The Web App opens the proposal under Requests. The members of the Guardian Team approve it on their devices, in the mobile app. When the vote passes, the connected app appears under Connected Apps.

Test the sign-in

In the Web App

In the Web App, open Connected Apps, find the new connected app and click Log in. Some service providers, such as Iru, accept only a sign-in that starts on their side. For those, the Web App first sends you to the service provider, which sends you back. The Web App then shows the details of the connected app. If the page asks for a value, such as a NameID, enter it. To leave a note for the approvers, open Advanced Options and fill in Reason for access. Click Log in again. The members of the Guardian Team approve the sign-in on their devices, in the mobile app. When the vote passes, click Login on the proposal page to finish the sign-in at the service provider.

With the default NameID, Built from each person’s email, you do not enter an email. SplitSecure sends the email of your own identity as the NameID.

  1. In the test profile, open https://<subdomain>.pagerduty.com.
  2. Click Sign in with SSO.
  3. The service provider sends you to the Web App, which opens the Log in page for the connected app. If the page asks for a value, enter it. Click Log in. The members of the Guardian Team approve the sign-in on their devices, in the mobile app. When the vote passes, click Login to return to the service provider, signed in.

In PagerDuty

Once both sign-ins work:

  1. Go to Settings → Single Sign-On.
  2. Uncheck Allow username/password login.
  3. Click Save Changes.

Removing SSO access does not remove the user from PagerDuty. When someone leaves, remove them from schedules and escalation policies, then delete or deactivate their PagerDuty user.

Troubleshooting

Issue Solution
PagerDuty shows “An unexpected error occurred” on save The certificate text is malformedPaste the whole PEM format file, with its BEGIN and END lines and no edits
PagerDuty reports a certificate error at sign-in The certificate does not match the identity providerDownload the certificate again from the SAML endpoints card and paste it
PagerDuty reports that the user is not authorized The user does not exist and auto-provisioning is offTurn on Auto-provision users on first login, or create the user in PagerDuty
PagerDuty says “Email address … is not allowed. Email addresses must use this domain” The NameID email is not on a domain the PagerDuty account allowsAdd the domain under Settings → Account Settings → Email Domain Restriction in PagerDuty, then click Update Email Domain Settings. Otherwise, sign in with an identity whose email is on an allowed domain
<subdomain>.pagerduty.com shows nginx “400 Bad Request, Request Header Or Cookie Too Large” after repeated failed sign-ins PagerDuty cookies piled up in the browserDelete the site data for pagerduty.com, fix the cause of the failed sign-in, then try again
PagerDuty still signs in with a password Allow username/password login is onTurn it off in Turn off password sign-in

External resources