XMatters cloud application

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

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

Set up SSO via SAML for XMatters

Before configuring SSO, ask XMatters support to provide a unique account ID for your organization. For example, the account ID for your account could be your-acc-id in https://your-acc-id.xmatters.com.This is provided by XMatters after registration.

Step 1: Set up Google as a SAML identity provider (IdP)
Sign in to your Google Admin console.

Sign in using an account with super administrator privileges (does not end in @gmail.com).

  1. From the Admin console Home page, go to Appsand thenSAML apps.
  2. Click the plus (+) icon at the bottom right. 
  3. Locate and click XMatters in the application list.
  4. On the Google IDP Information page:
    • Copy and save the SSO URL and Entity ID.
    • Download the Certificate.
  5. Click Next.

    The Basic information window shows the Application name and Description seen by users.

  6. Click Next.
  7. On the Service Provider Details page, edit the ACS URL, Entity ID, and Start URL, replacing {your-account-id} with the account ID from XMatters. 
  8. Click Finish.
Step 2: Set up XMatters as a SAML 2.0 service provider (SP)
  1. Open a new incognito browser window.
  2. Sign in to https://{your-account-id}.xmatters.com with your organization's XMatters administrator account.
  3. In the XMatters home page, click Admin.

  4. On the left, click Company Details.

  5. Under SAML Configuration on the right, click Enable SAML

  6. In the Identity Provider ID field, enter the Entity ID you copied in step 1.

  7. In the Audience field, enter https://{your-account-id}.xmatters.com.

  8. In the Single Sign On URL field, enter the SSO URL you copied in step 1.

  9. From the Identifier Type list, select Web Login ID.

  10. From the Identifier Location list, select Subject NameID.

  11. In the SAML Certificate field, paste the certificate you downloaded in step 1.

  12. Click Save Changes.
Step 3: Enable the XMatters app
  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 Appsand thenSAML apps.
  3. Select XMatters.
  4. Click User access.
  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. (Optional) Turn on the service for a group of users.
    Use access groups to turn on a service for specific users within or across your organizational units. Learn more

  8. Ensure that your XMatters user account email IDs match those in your Google domain.
Step 4: Verify that the SSO is working

Note: XMatters only supports IdP initiated SSO. You can’t use SSO if you sign in directly to XMatters.

  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 Appsand thenSAML apps.
  3. Select XMatters.
  4. At the top left, click Test SAML login

    XMatters should open in a separate tab. If it doesn’t, use the information in the resulting SAML error messages to update your IdP and SP settings as needed, then retest SAML login.

You should be automatically redirected to your XMatters account.


Google, G Suite, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.
Was this helpful?
How can we improve it?