Pagerduty cloud application

You must be signed in as a super administrator for this task.

Using Security Assertion Markup Language (SAML), your users can use their Google Cloud credentials to sign in to enterprise-cloud applications.

Set up SSO via SAML for Pagerduty

Here's how to set up single sign-on (SSO) via SAML for the Pagerduty® application.

Step 1: Set up Pagerduty as a SAML 2.0 service provider (SP)
  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Security, and then the SSO settings:

    You must be signed in as a super administrator for this task.

    Click Set up single sign-on (SSO) for SAML applications.

    Or, if you don’t have that option:

    Click Set up single sign-on (SSO).

  3. Copy the SSO URL.
  4. Click the Download button to download the X.509 Certificate.
  5. In a new browser tab, go to the Pagerduty SAML Configuration Page (https://signup.pagerduty.com/accounts/new).
  6. Select Configuration > Account Settings > Single Sign-on.
  7. Click SAML in the sidebar.
  8. Upload the X.509 Certificate required for SSO setup you downloaded in Step 4.
  9. Paste the Login URL from the Google Admin console SAML settings into the Sign-in page URL field in Pagerduty.
  10. Filling in the Sign-out page URL field is optional. You can leave it empty. 
  11. Add SAML permissions to user roles.
  12. Click Submit and proceed to the next section to set up Google as a SAML identity provider (IdP).
Step 2: Set up Google as a SAML identity provider (IdP)
  1. In a new browser tab, sign in to your Admin console as a super administrator.
  2. Click Apps SAML apps.
  3. Click the plus (+) icon in the bottom corner.
  4. Select the Pagerduty item from the list. The values on the Google IDP Information page automatically populate.
  5. In the Basic application information window, the Application name and Description values automatically populate.
  6. Click Next.
Step 3: Enter service provider details in Google Admin console
  1. In the Service Provider Details section, enter the following URLs into the Entity IDACS URL, and Start URL fields:
            ACS URL: https://your-subdomain.pagerduty.com/sso/saml/consume
            Entity ID: https://your-subdomain.pagerduty.com
            Start URL: empty.
  2. Leave Signed Response unchecked. This is specified in the metadata file. You may override it if needed.
    When the Signed Response checkbox is unchecked, only the assertion is signed. When the Signed Response checkbox is checked, the entire response is signed.
  3. ​The default Name ID is the primary email. Multi-value input is not supported. You can change the Name ID mapping as per your requirement. Custom attributes of the user schema can also be used after creating them via Google Admin SDK APIs. The custom attributes for the user schema need to be created prior to setting up the Pagerduty SAML application.  
  4. Click Finish.
Step 4: Enable the Pagerduty app
  1. Sign in to your Admin console.
  2. Go to Apps SAML apps.
  3. Select Pagerduty.
  4. At the top right of the gray box, click Edit Service Compose.

  5. To turn on or off a service for everyone in your organization, click On for everyone or Off for everyone, and then click Save.

  6. To turn on or off a service only for users in an organizational unit:

    1. At the left, select the organizational unit.
    2. Select On or Off.
    3. To keep the service turned on or off even when the service is turned on or off for the parent organizational unit, click Override.
    4. If the organization's status is already Overridden, choose an option:
      • Inherit—Reverts to the same setting as its parent.
      • Save—Saves your new setting (even if the parent setting changes).

    Learn more about organizational structure.

  7. Ensure that your Pagerduty user account email IDs match with those in your Google domain.
Step 5: Verify that the SSO is working 
  1. Open https://your-subdomain.pagerduty.com. You should be automatically redirected to the Google sign in page.
  2. Enter your sign in credentials.
  3. After your sign in credentials are authenticated you are automatically redirected back to Pagerduty.
Was this helpful?
How can we improve it?