As business applications move from on-premises to cloud hosted solutions, users experience password fatigue due to disparate logons for different applications. Single sign-on (SSO) technologies seek to unify identities across systems and reduce the number of different credentials a user has to remember or input to gain access to resources.
While SSO is convenient for users, it presents new security challenges. If a user's primary password is compromised, attackers may be able to gain access to multiple resources. In addition, as sensitive information makes its way to cloud-hosted services it is even more important to secure access by implementing two-factor authentication.
Duo Access Gateway (DAG), our on-premises SSO product, layers Duo's strong authentication and flexible policy engine on top of New Relic logins using the Security Assertion Markup Language (SAML) 2.0 authentication standard. Duo Access Gateway acts as an identity provider (IdP), authenticating your users using existing on-premises or cloud-based directory credentials and prompting for two-factor authentication before permitting access to New Relic.
Duo Access Gateway is included in the Duo Beyond, Duo Access, and Duo MFA plans, which also include the ability to define policies that enforce unique controls for each individual SSO application. For example, you can require that Salesforce users complete two-factor authentication at every login, but only once every seven days when accessing New Relic. Duo checks the user, device, and network against an application's policy before allowing access to the application.
Add the attributes from the table below that correspond to the Duo attributes Mail attribute and Username attribute in the "Attributes" field when configuring your Active Directory or OpenLDAP authentication source in the DAG admin console, separated by a comma. For example, if Active Directory is your authentication source, enter mail,sAMAccountName in the "Attributes" field.
|Duo Attribute||Active Directory||OpenLDAP|
If your organization uses other directory attributes than the ones listed here then enter those attribute names instead. If you've already configured the attributes list for another cloud service provider, append the additional attributes not already present to the list, separated by a comma.
After completing the initial DAG configuration steps, click Applications on the left side of the Duo Access Gateway admin console.
Scroll down the Applications page to the Metadata section. This is the information you need to provide to New Relic when configuring SSO. Click the Download Certificate link to obtain the token signing certificate (the downloaded file is named "dag.crt").
Log on to the Duo Admin Panel and navigate to Applications.
Click Protect an Application and locate the "Duo Access Gateway (self-hosted)" entry for New Relic in the applications list. Click Protect to the far-right to start configuring New Relic. See Protecting Applications for more information about protecting applications in Duo and additional application options.
The Account number is the account number associated with your New Relic account. For example, if your New Relic URL when logged in is https://rpm.newrelic.com/accounts/1234567, enter 1234567.
New Relic uses the Mail attribute when authenticating. We've mapped Mail attribute to DAG supported authentication source attributes as follows:
|Duo Attribute||Active Directory||OpenLDAP||SAML IdP||Azure|
If you are using a non-standard email attribute for your authentication source, check the Custom attributes box and enter the name of the attribute you wish to use instead.
Click Save Configuration to generate a downloadable configuration file.
You can adjust additional settings for your new SAML application at this time — like changing the application's name from the default value, enabling self-service, or assigning a group policy — or come back and change the application's policies and settings after you finish SSO setup. If you do update any settings, click the Save Changes button when done.
Click the Download your configuration file link to obtain the New Relic application settings (as a JSON file).
Important: This file contains information that uniquely identifies this application to Duo. Secure this file as you would any other sensitive or password information. Don't share it with unauthorized individuals or email it to anyone under any circumstances!
Before you do this, verify that you updated the "Attributes" list for your Duo Access Gateway authentication source as specified here.
Return to the Applications page of the DAG admin console session.
Click the Choose File button in the "Add Application" section of the page and locate the New Relic SAML application JSON file you downloaded from the Duo Admin Panel earlier. Click the Upload button after selecting the JSON configuration file.
The New Relic SAML application is added.
Add the Duo Access Gateway as a new single sign-on provider for New Relic.
Log into the New Relic site as an administrator. In the right-hand corner navigate to your account name and click on Account settings. On the new page click the Single sign-on link on the left hand navigation bar.
The "Your SAML Identity Provider certificate" is the DAG Metadata certificate supplied by Duo Access Gateway. Click Browse files... to select the dag.crt file you downloaded from the DAG admin console "Application" page earlier.
Copy the SSO URL information from the Duo Access Gateway admin console Metadata display and paste it into the New Relic Remote login URL field.
Copy the Logout URL information from the Duo Access Gateway admin console Metadata display and paste it into the New Relic Logout landing URL (optional) field.
After you've entered all the required information click Save my changes.
On the page "Test your SAML configuration" click Test SAML Login. This automatically redirects you to the Duo Access Gateway to sign in with your SSO account. Once you've successfully logged in with the Duo Access Gateway you'll be redirected back to the New Relic site.
On the page "Enable SAML for your account" click Enable SAML login. This will automatically sign you out of your accounts and ask you to sign back in using the Duo Access Gateway.
Learn more about New Relic SSO at the New Relic Support Site.
You can log on to New Relic using the normal login page. Once you've typed your e-mail address clicking "Sign In" redirects you to the Duo Access Gateway login page. Enter your primary directory logon information, approve Duo two-factor authentication, and get redirected back to the New Relic site after authenticating.
If using the New Relic mobile app, enter your federated e-mail address and tap "Next", and then authenticate to Duo Access Gateway.
Congratulations! Your New Relic users now authenticate using Duo Access Gateway.
If you plan to permit use of WebAuthn authentication methods (security keys, U2F tokens, or Touch ID), Duo recommends enabling hostname whitelisting for this application and any others that show the inline Duo Prompt before onboarding your end-users.
Microsoft's Active Directory Federation Services (AD FS) is a popular choice for SSO because it easily integrates with the AD identity store many organizations already have deployed. Duo's support for cloud applications and SSO drops in to an existing AD FS installation to provide secondary authentication after a user passes primary authentication (successful Active Directory logon).
If you don't already have AD federation running the first step is to install and configure Microsoft AD FS in your organization. Deployment Guides for AD FS versions 2.1, and 3.0/4.0 are available from Microsoft.
Once your AD FS services are up and running, the second step is to configure the SSO partnership between your AD FS service and the external cloud resource, in this case New Relic. Learn more about configuring New Relic SSO with AD FS at the New Relic Support Site.
After you have successfully configured and tested AD FS SSO login to New Relic using your AD domain credentials, you can then install the Duo AD FS integration. AD FS protection is included with Duo's paid plans.
With the Duo integration for AD FS installed, users pass primary authentication to the AD FS service as usual. Once primary authentication succeeds, users are forwarded to the Duo service for secondary authentication. After approving logon using one of Duo's authentication methods, the user is fully logged in to New Relic.
Using a third-party SSO provider for cloud application access? Duo partners with leading cloud SSO providers like Okta and OneLogin to secure access with our strong and flexible authentication platform.