> For AI agents: [llms.txt](https://docs.trustedauth.com/llms.txt) provides a Markdown index of this documentation.

# PingDom

PingDom offers a cloud-based incident management platform for IT departments (see <https://www.pingdom.com>). You can protect access to PingDom by integrating PingDom with Identity as a Service. Once integrated, users can use single sign-on to log in to their PingDom account through Identity as a Service.

note

This integration was tested using Identity as a Service version 5.30 and PingDom version June 2021. Other versions of PingDom may require integration and configuration steps that differ from those documented in this procedure. For other versions of PingDom, use this procedure as a starting point for integrating PingDom. In the event of other issues, contact <support@entrust.com> for assistance.

To integrate PingDom with Identity as a Service, you must do the following

Before you begin, open two browser windows. In one window, log in to your PingDom administrator account. In the other window, log in to your IDaaS administrator account.

## Step 1: Obtain the Entity ID and ACS URL from PingDom

1. From the PingDom home page, click the cogwheel icon **> Security**. The **Security** page appears.
2. Click **SAML**. The **SAML** page appears.
3. Click the **Configuration** tab. It should be the default landing page.
4. Leave this page open to return to it in _Step 2: Add PingDom to Identity as a Service._

## Step 2: Add PingDom to Identity as a Service

1. In Identity as a Service, click Menu icon **>** **Security > Applications**. The **Applications** **Lists** page appears.
2. Click **Add**. The **Select an Application Template** page appears.
3. Do one of the following:
   - Select **SAML Cloud Integrations** from the search drop-down list and scroll to find the application you want to add to IDaaS.
   - In the **Search bar**, enter a search option to filter for the application you want to add to IDaaS.
4. Click **PingDom**. The **Add PingDom** page appears.
5. Enter an **Application Name**.
6. Enter an **Application Description**.
7. Optional. Add a custom application logo.
   1. Click Plus icon next to **Application Logo**. The **Upload Logo** dialog box appears.
   2. Click Upload icon to select an image file to upload.
   3. Browse to select your file and click **Open**. The **Upload Logo** dialog box reappears showing your selected image.
   4. If required, resize your image.
   5. Click **OK**.
8. Select the **Authentication Flow** that appears to users during login.
9. Click **Next**. The **General** page appears.
10. Return to the PingDom window and copy paste the following:
    1. Copy the PingDom **ACS URL** and paste in the IDaaS **Assertion Consumer Service URL** field.
    2. Copy the PingDom **Entity ID** and paste it in the IDaaS **Entity ID** field.
11. If available, use the **Upload Metadata XML** file option to auto-populate the following fields, if available in the file: Default Assertion Consumer Service URL, Alternative Assertion Consumer URLs, Service Provider Entity ID (Issuer), Single Logout Service URL, SAML Signing Certificate, SAML NameID Encoding Format, SAML Signature Algorithm.
    1. Click Upload icon to the **Upload Metadata XML** and browse to the location of the metadata file you downloaded. The **Metadata Configuration** dialog box appears.
    2. If required, click **Merge with existing values** to merge new values with existing values for Alternative Assertion Consumer Services URLs and SAML attribute names.
    3. Click **Save**.
12. Optional. Enter the **SAML Username Parameter Name** used to identity the user ID being requested for authentication. The user ID can then be passed as a parameter, for example, Username=jdoe. Alternately, if the SAML username is NameID, the SAML Request XML NameID element value is used to the identify the IDaaS userID.
13. Enter the **SAML Session Timeout** to the time when the SAML Assertion times out. The maximum is 720 minutes.
14. From the **SAML NameID Attribute** drop-down list, select **Email**.
15. From the **SAML NameID Encoding Format** drop-down list, select **Email**.
16. Select the **SAML Signing Certificate** from the drop-down list.
17. From the **SAML Signature Algorithm** drop-down list, select **SHA512**.
18. Select **Sign Complete URL Response**.
19. Deselect **Enable Go Back Button** if you do not want users to be able to go back to the PingDom login page to log in.
20. Select **Show Default Assertion Consumer URL Service in the My Profile**. When selected, the Default Assertion Consumer URL appears in a user's My Profile page in addition to relay states and Alternative Assertion Consumer URLs.
21. Optional. Add **Alternative Assertion Consumer Service URLs**, as follows:
    1. Click **Add**.
    2. Enter a **Name**.
    3. Enter a URL **Value**.
    4. Select **Show in My Profile** to display the Alternative Consumer Service URL in a user's My profile page.
    5. Optional. **Add an Application Logo**.
    6. Click **Add**.
    7. Repeat these steps to add more Alternative Assertion Consumer Service URLs.
22. Click **Submit**.

## Step 3: Add a resource rule

See [Create resource rules](/docs/authentication-and-security/create-and-manage-resource-rules.md).

## Step 4: Copy the SAML configurations from Identity as a Service

1. Log into your Identity as a Service administrator account.
2. Click Menu icon **>** **Security > Applications**. The **Applications** **Lists** page appears.
3. Under **SAML Cloud Integrations**, click **SAML Configuration**. The **SAML Configuration** dialog box appears. This dialog box contains information you need to configure your SAML application for Identity as a Service authentication.
4. Do one of the following:
   - Leave this dialog box open to reference later in this procedure.
   - Copy the Entity ID, Single Sign-on URL, and Single Logout URL to a text file and save it to reference later in this procedure.

note

Depending on the integration you are performing, you may not need all three of these SAML configuration values.

## Step 5: Copy the SAML signing certificate from Identity as a Service

1. Log in to your Identity as a Service administrator account.
2. Click Menu icon **>** **Security > Applications**. The **Applications List** page appears.
3. Under **SAML Cloud Integrations**, click **SAML Signing Certificates**. The **SAML Signing Certificates** page appears.
4. Click the copy icon next to the certificate to copy it to the clipboard. You can additionally download the certificate and save it for future use.
5. Open a text editor, such as Notepad, and paste the contents of the certificate into the text file.
6. Save the file.

note

Be sure to same the file with the .cer extension, for example, SAML_certifcate.cer.

## Step 6: Configure PingDom for Identity as a Service authentication

1. Return to the **PingDom** SAML Configuration page.
2. Open the text file you created in _Step 4: Copy the SAML Configurations from Identity as a Service_ and do the following:
   1. In the **Entity ID** field, paste the **Entity ID** you copied from IDaaS.
   2. In the **ACS URL** field, enter the **Single Sign-On URL** from IDaaS.
3. Open the text file you created in _Step 5: Copy the SAML Certificate from Identity as a Service_ and do the following:
   1. In the **Certificate** field, paste the SAML Certificate you copied from IDaaS.
4. Toggle to **Enable SAML Integration**.
5. Click **Save**.

## Step 7: Test the integration

### Testing Service Provider Login

1. Open a Web browser and enter the URL for your PingDom account. You are directed to Identity as a Service.
2. Enter your PingDom account **User ID** and click **Next**.
3. Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to PingDom.

### Testing Identity as a Service redirect log in

1. Log in to your Identity as a Service account.
2. Go to your **My Profile** page if you are not already there.
3. Under **Applications**, click **PingDom**.
4. Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to PingDom.

Testing Identity as a Service redirect log in

Log in to your Identity as a Service account.

Go to your **My Profile** page if you are not already there.

Under **Applications**, click **PingDom**.

Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to PingDom.