> For AI agents: [llms.txt](https://docs.trustedauth.com/llms.txt) provides a Markdown index of this documentation. # New Relic New Relic is a Web application performance service that works in real-time with live Web apps. (see ). You can protect access to New Relic by integrating New Relic with Identity as a Service. Once integrated, users can use single sign-on to log in to their New Relic account through Identity as a Service. note This integration was tested using Identity as a Service version 5.17 and New Relic Release. Other versions of New Relic may require integration and configuration steps that differ from those documented in this procedure. For other versions of New Relic, use this procedure as a starting point for integrating New Relic. In the event of other issues, contact for assistance. ## Before you begin New Relic has two user models: - Original user model: New Relic organization created before July 30, 2020. - New Relic One user model: Model used by Identity as a Service. attention If you did not migrate your original New Relic user model to New Relic One, you need to migrate to the **New Relic One user model** before you begin the integration with Identity as a Service. For more information, see . To integrate New Relic One with Identity as a Service, complete the following steps. ## Step 1: 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 2: Export 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 download icon next to the certificate to export the certificate you want to import into your SAML service provider application. The **Export Certificate** dialog box appears. 5. If the certificate has been issued by a CA, do one of the following: - Click **Certificate** to export the self-signed certificate. - Click **Root CA Certificate** to export a certificate issued from a CA. - Click **Certificate Chain** to export the SAML signing certificate and its CA certificates. 6. Click **Export**. ## Step 3: Configure New Relic for Identity as a Service 1. In a Web browser, enter . 2. Log in to your New Relic administrator account. 3. Click the menu icon and select **Administration** from the drop-down menu. The **Administration** page appears. 4. Click **Organization & access**. The **Organization** page appears. 5. Click **Authentication Domains**. The **Authentication Domains** page appears. 6. In the **Authentication** pane, click **Configure** and then do the following: 1. For **Method of authenticating users**, select **SAML SSO**. 2. Open a text editor such as Notepad and copy and save the **Assertion consumer URL** and the **Our entity ID** URL. You need these URLs in _Step 4: Add New Relic to Identity as a Service_. 3. Scroll to **Source of SAML Metadata** and select **Upload a certificate**. 4. Click **Choose File**, and browse to select the SAML certificate you exported in _Step 2: Export the SAML signing certificate from Identity as a Service_. 5. In the **SSO target URL** field, paste the **Single Sign-On URL** you copied in _Step 1: Copy the SAML configurations from Identity as a Service_. 6. Scroll to the top of the **Authentication** pane and click **Save**. 7. Click **Save Changes** on the confirmation prompt. ## Step 4: Add New Relic to 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. Click **Add**. The **Select an Application Template** page appears. 4. 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. 5. Click **New Relic**. The **Add New Relic** page appears. 6. Enter an **Application Name**. 7. Enter an **Application Description**. 8. 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**. 9. Select the **Authentication Flow** that appears to users during login. 10. Click **Next**. The **General** page appears. 11. In the **Default** **Assertion Consumer Service URL** field enter the **Assertion consumer URL** you copied in _Step 3: Configure New Relic for Identity as a Service_. 12. In the **Service Provider Entity ID (Issuer)** field enter the **Our entity ID** URL you copied in _Step 3: Configure New Relic for Identity as a Service_. 13. 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. 14. Enter the **SAML Session Timeout** to the time when the SAML Assertion times out. The maximum is 720 minutes. 15. From the **SAML NameID Attribute** drop-down list, select **Email**. 16. From the **SAML NameID Encoding Format** drop-down list, select **Email**. 17. From the **SAML Signature Algorithm** drop-down list, select **SHA512**. 18. Select the **SAML Signing Certificate** from the drop-down list. 19. Select **Sign Complete SAML Response**. 20. Deselect **Enable Go Back Button** if you do not want users to be able to go back to the New Relic login page to log in. 21. 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. 22. 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. 23. Click **Submit**. ## Step 5: Add a resource rule See [Create resource rules](/docs/authentication-and-security/create-and-manage-resource-rules.md). ## Step 6: Test the integration ### Testing Service Provider Login 1. Open a Web browser and enter the URL for your New Relic account. You are directed to Identity as a Service. 2. Enter your Mew Relic account **User ID** and click **Next**. 3. Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to New Relic page. ### 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 **New Relic**. 4. Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to New Relic.