Skip navigation
Documentation

Duo Protection for Bugsnag

Duo offers a variety of methods for adding two-factor authentication and flexible security policies to Bugsnag SSO logins, complete with inline self-service enrollment and Duo Prompt.

Overview

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

Duo Access Gateway (DAG), our on-premises SSO product, layers Duo's strong authentication and flexible policy engine on top of Bugsnag logins using the Security Assertion Markup Language (SAML) 2.0 authentication standard. Duo Access Gateway authenticates your users using existing on-premises or cloud-based directory credentials and prompts for two-factor authentication before permitting access to Bugsnag.

Duo Access Gateway is part of the Duo Beyond and Duo Access plans, so you can 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 Bugsnag. Duo checks the user, device, and network against an application's policy before allowing access to the application.

Deploy Duo Access Gateway

  1. Install Duo Access Gateway on a server in your DMZ. Follow our instructions for deploying the server, configuring DAG settings, and adding your primary authentication source.

  2. Add the attributes from the table below that correspond to the Duo attributes Mail attribute, First name attribute, and Last name 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,givenName,sn in the "Attributes" field.

    Duo Attribute Active Directory OpenLDAP
    Mail attribute mail mail
    First name attribute givenName gn
    Last name attribute sn sn

    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.

  3. After completing the initial DAG configuration steps, click Applications on the left side of the Duo Access Gateway admin console.

  4. Scroll down the Applications page to the Metadata section. This is the information you need to provide to Bugsnag when configuring SSO.

    DAG Metadata Information

Create the Bugsnag Application in Duo

  1. Log on to the Duo Admin Panel and navigate to Applications.

  2. Click Protect an Application, locate SAML - Bugsnag in the applications list, and click Protect this Application. See Getting Started for help.

  3. Enter the organization ID used when logging into your company's Bugsnag portal as the Organization ID. For example, if your Bugsnag login URL is app.bugsnag.com/your-company then enter your-company.

  4. Bugsnag uses the Mail attribute, First name attribute, and Last name attribute when authenticating. We've mapped those to DAG supported authentication source attributes as follows:

    Duo Attribute Active Directory OpenLDAP SAML IdP Google Azure
    Mail attribute mail mail mail email mail
    First name attribute givenName gn givenName given_name givenName
    Last name attribute sn sn sn family_name surname

    If you are using non-standard attributes for your authentication source, check the Custom attributes box and enter the names of the attributes you wish to use instead.

  5. Click Save Configuration to generate a downloadable configuration file.

    Duo Bugsnag Application Settings

  6. 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.

  7. Click the Download your configuration file link to obtain the Bugsnag 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!

Add the Bugsnag Application to Duo Access Gateway

  1. Return to the Applications page of the DAG admin console session.

  2. Click the Choose File button in the "Add Application" section of the page and locate the Bugsnag SAML application JSON file you downloaded from the Duo Admin Panel earlier. Click the Upload button after selecting the JSON configuration file.

  3. The Bugsnag SAML application is added.

    Bugsnag Application Added

Configure Bugsnag SSO

Add the Duo Access Gateway as a new single sign-on provider for Bugsnag.

  1. Log into Bugsnag as an administrative user. Click on your user icon in the upper right-hand corner of the page. Click Settings from the dropdown.

  2. On the "Settings" page click Organization.

  3. On the "Organization" page next to "Authentication" click Single sign-on. A new window will open.

  4. Copy the Entity ID URL from the Duo Access Gateway admin console metadata display and paste it into the Bugsnag Login URL from your SSO provider field.

    Example: https://yourserver.example.com/dag/saml2/idp/metadata.php

  5. Optionally you can check the box next to Auto-provision users on first login to automatically create new Bugsnag user accounts on first SSO login if they do not already exist. You will still need to assign permissions to those users manually.

  6. Once you've entered all required information click Enable SSO.

    Bugsnag Single Sign-On Setting Edit

Learn more about Bugsnag SSO at Bugsnag Docs.

Verify SSO

If your organization enabled the Duo Access Gateway portal, log into the portal page using the link provided by your administrator. Click Bugsnag from the dashboard to access the application.

You can also log into Bugsnag by going to the Bugsnag login page. Click Sign in with your identity provider. Enter your organization ID into the field and click Sign in using your identity provider. This redirects to the Duo Access Gateway login page. Enter your primary directory logon information, approve Duo two-factor authentication, and get redirected back to Bugsnag after authenticating.

DAG Login and Authentication Prompt

Congratulations! Your Bugsnag users now authenticate using Duo Access Gateway.

Enforce SSO

By default we've set Bugsnag to allow users to sign in either with their username and password or SSO. You can modify this setting to mandate SSO for logging into Bugsnag.

  1. While logged into Bugsnag as an administrative user, click on your user icon in the top right-hand corner of the page. Click Settings from the dropdown.

  2. On the "Settings" page click Organization.

  3. On the "Organization" page next to "Authentication" click Single sign-on. A new window will open.

  4. Check the box next to Force your team to log in via your SSO provider.

  5. Click Save.

    Bugsnag Single Sign-On Setting to enforce SSO

Microsoft AD FS

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. Microsoft's Deployment Guides for AD FS versions 2.0, 2.1, and 3.0 are available on the TechNet site.

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 Bugsnag. Learn more about configuring Bugsnag SSO with AD FS at the Bugsnag Docs site.

After you have successfully configured and tested AD FS SSO login to Bugsnag 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 Bugsnag.

Other Identity Partners

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.

You can also use Duo two-factor authentication with CAS and Shibboleth on-premises IdPs.

Troubleshooting

Need some help? Try searching our Knowledge Base articles or Community discussions. For further assistance, contact Support.

Ready to Get Started?

Sign Up Free