PingOne for Enterprise

Adding New Relic to Your PingOne for Enterprise Dock

Add the New Relic application your PingOne for Enterprise Dock from the application catalog.

Steps

  1. In the PingOne for Enterprise admin console, go to Applications → Application Catalog.

  2. Optional: In the Search field, search for the application.

  3. Click the New Relic application line to expand it and click Setup.

  4. On the SSO Instructions tab, click Download to download the signing certificate.

  5. In a separate tab or window, sign on to your New Relic account as an administrative user.

  6. In New Relic, go to Account Settings → Integrations → Single Sign On → Configure.

  7. On the Your SAML Identity Provider Certificate line, click Upload to upload the signing certificate you downloaded in step 4.

  8. In the Your SAML Identity Provider Details field, enter https://sso.connect.pingidentity.com/sso/idp/SSO.saml2?idpid=<IdP ID>, replacing <IdP ID> with your IdP ID value from PingOne.

  9. On the New Relic SAML Service Provider Details line, copy the Assertion Consumer Service URL for use in a future step.

  10. Click Save My Changes.

  11. Click Login With SAML to test your settings.

  12. After a successful test, click Enable SSO.

Next steps

In PingOne for Enterprise, click Continue to Next Step.

New Relic Connection Configuration

Steps

  1. Import the metadata for New Relic:

    Choose from:

    • Click Select File to upload the metadata file.

    • Click Or use URL to enter the URL of the metadata.

  2. In the ACS URL field, enter the Assertion Consumer Service URL value that you copied previously.

  3. In the Entity ID field, enter the entity ID value.

    The pre-populated value for this field should work for most configurations.

  4. In the Target Resource field, enter a URL to redirect the user to after IdP-initiated single sign-on (SSO).

  5. In the Single Logout Endpoint field, enter a URL for PingOne to send single logout (SLO) requests to.

  6. In the Single Logout Response Endpoint field, enter a URL for PingOne to send SLO responses to.

  7. To add a Primary Verification Certificate, click Browse to locate and upload a local certificate file used to verify SLO requests and responses coming from New Relic.

  8. To add a Secondary Verification Certificate, click Browse to locate and upload a local certificate used to verify SLO requests and responses if the primary certificate fails.

  9. Select the Force Re-authentication check box to require your identity bridge to re-authenticate users with an active SSO session.

  10. Select the Encrypt Assertion check box to encrypt outgoing SAML assertions.

  11. On the Signing line:

    Choose from:

    • Click Sign Assertion to have PingOne sign outgoing SAML assertions. This is the default option.

    • Click Sign Response to have PingOne sign responses to incoming SAML assertions.

  12. From the Signing Algorithm list, select an algorithm with which to sign SAML assertions.

  13. Select the Use Custom URL check box to enter a customer URL to launch New Relic from the dock.

Next steps

Click Continue to Next Step.

New Relic Attribute Mapping

About this task

PingOne will automatically populate required SAML attributes.

For New Relic, the required attribute is SAML_SUBJECT. Map it to an attribute that matches the user email address. Click Advanced and from the Name ID Format to send to SP list, select urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress.

Steps

  1. To add an additional optional attribute, click Add new attribute.

  2. In the Application Attribute field, enter the attribute name as it appears in the application.

  3. In the Identity Bridge Attribute or Literal Value field, choose one of the following:

    Choose from:

    • To map to the application attribute: Enter or select a directory attribute.

    • To assign to the application attribute: Select As Literal, then enter a literal value.

  4. To create advanced attribute mappings, click Advanced.

    For more information, see Create advanced attribute mappings.

Next steps

Click Continue to Next Step.

New Relic Customization

Steps

  • To change the application icon, click Select image and upload a local image file.

    The image file must be:

    • PNG, GIF, or JPG format

    • 312 x 52 pixels maximum

    • 2 MB maximum file size

      Images are scaled to 64 x 64 pixels for display.

  • To change the name of the application displayed on the dock, in the Name field, enter a new name.

  • To change the description of the application, in the Description field, enter the new description text.

  • To change the category to which the application is assigned on the dock, in the Category list, select a category.

    For information about creating custom application categories, see Creating a custom application category.

Next steps

Click Continue to Next Step.

New Relic Group Access

About this task

The Group Access tab shows every user group that you have created.

For more information about creating user groups, see Add user groups.

Steps

  • To add a group’s access to the application, on the line for that group, click Add.

  • To remove a group’s access, on the line for that group, click Remove.

  • When you’re finished assigning groups, click Continue to Next Step.

Next steps

On the Review Setup tab, review your configuration, and click Finish to add the application to your PingOne Dock.