Duo Single Sign-On for GitHub Enterprise

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 and zero-trust policies.

About Duo Single Sign-On

Duo Single Sign-On is our cloud-hosted SSO product which layers Duo's strong authentication and flexible policy engine on top of GitHub Enterprise logins. Duo Single Sign-On acts as an identity provider (IdP), authenticating your users using existing on-premises Active Directory (AD) or another SSO IdP. Duo SSO prompts users for two-factor authentication and performs endpoint assessment and verification before permitting access to GitHub Enterprise.

Duo Single Sign-On is available in Duo Premier, Duo Advantage, and Duo Essentials 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 GitHub Enterprise. Duo checks the user, device, and network against an application's policy before allowing access to the application.

Configure Single Sign-On

Before configuring GitHub Enterprise with Duo SSO using Security Assertion Markup Language (SAML) 2.0 authentication you'll first need to enable Duo Single Sign-On for your Duo account and configure a working authentication source.

Once you have your SSO authentication source working, continue to the next step of creating the GitHub Enterprise application in Duo.

Create GitHub Enterprise Application in Duo

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

2. Click Protect an Application and locate the entry for GitHub Enterprise with a protection type of "2FA with SSO hosted by Duo (Single Sign-On)" in the applications list. Click Protect to the far-right to start configuring GitHub Enterprise. See Protecting Applications for more information about protecting applications in Duo and additional application options. You'll need the information on the GitHub Enterprise page under Metadata later.

3. GitHub Enterprise uses the Username attribute when authenticating. We've mapped the bridge attribute to Duo Single Sign-On supported authentication source attributes as follows:

   Bridge Attribute	Active Directory	SAML IdP
   <Username>	sAMAccountName	Username

   If you are using a non-standard attribute for your authentication source, click the Custom attributes checkbox and enter the name of the attribute you wish to use instead.

   

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

5. Scroll to the bottom of the page and click the Save button. Leave this page open as you'll need this information later.

Duo Universal Prompt

The Duo Universal Prompt provides a simplified and accessible Duo login experience for web-based applications, offering a redesigned visual interface with security and usability enhancements.

Universal Prompt	Traditional Prompt

We've already updated the Duo GitHub Enterprise application hosted in Duo's service to support the Universal Prompt, so there's no action required on your part to update the application itself. If you created your GitHub Enterprise application before March 2024, you can activate the Universal Prompt experience for users from the Duo Admin Panel. GitHub Enterprise applications created after March 2024 have the Universal Prompt activated by default.

If you created your GitHub Enterprise application before March 2024, it's a good idea to read the Universal Prompt Update Guide for more information, about the update process and the new login experience for users, before you activate the Universal Prompt for your application.

Activate Universal Prompt

Activation of the Universal Prompt is a per-application change. Activating it for one application does not change the login experience for your other Duo applications.

The "Universal Prompt" area of the application details page shows that this application is "Ready to activate", with these activation control options:

• Show traditional prompt: Your users experience Duo's traditional prompt via redirect when logging in to this application.
• Show new Universal Prompt: (Default) Your users experience the Universal Prompt via redirect when logging in to this application.

The application's Universal Prompt status shows "Activation complete" here and on the Universal Prompt Update Progress report.

Should you ever want to roll back to the traditional prompt, you can return to this setting and change it back to Show traditional prompt. However, this will still deliver the Duo prompt via redirect, not in an iframe. Keep in mind that support for the traditional Duo prompt ended for the majority of applications in March 2024.

Universal Update Progress

Click the See Update Progress link to view the Universal Prompt Update Progress report. This report shows the update availability and migration progress for all your Duo applications. You can also activate the new prompt experience for multiple supported applications from the report page instead of visiting the individual details pages for each application.

Enable GitHub Enterprise SSO

Add Duo Single Sign-On as a new single sign-on provider in GitHub Enterprise.

1. Log on to your GitHub Enterprise account and click Settings in your profile drop-down menu. If your GitHub Enterprise account is not selected by default, click Switch to another account to select it.

2. Scroll down to the "Security" section in the left menu sidebar. Click Authentication security.

3. In the "SAML single sign-on" section, click the Enable SAML authentication checkbox.

   

4. Return to the Duo Admin Panel tab with the GitHub Enterprise application open. Copy the Issuer URL from the Duo Admin Panel and paste it into the GitHub Enterprise Issuer field.

   Example: https://sso-abc1def2.sso.duosecurity.com/saml2/sp/DIABC123678901234567/metadata

5. Copy the Sign on URL from the Duo Admin Panel and paste it into the GitHub Enterprise Sign on URL field.

   Example: https://sso-abc1def2.sso.duosecurity.com/saml2/sp/DIABC123678901234567/sso

   

6. In the Duo Admin Panel under "Downloads", click Copy certificate. Paste the copied certificate file text, including the -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines, into the GitHub Enterprise Public certificate field.

   

7. Look for the "The assertion consumer service URL is..." information on your GitHub Enterprise account page. Copy that URL and paste it in the Assertion consumer service URL field in the Duo Admin Panel.

   Example: https://github.com/orgs/acme/saml/consume

   

8. Scroll to the bottom of the GitHub Enterprise page in the Duo Admin Panel and click Save.

9. Return to your GitHub Enterprise account page. Scroll down the page and click Test SAML configuration.

10. Follow the on-screen prompts to log in with Duo. You are then redirected back to your GitHub Enterprise account page.

11. Scroll down to confirm the SAML configuration test passed and click Save.

Learn more about GitHub Enterprise SSO at GitHub Docs.

Using SSO

You can log on to GitHub Enterprise by navigating to your GitHub SSO page e.g., https://github.com/orgs/accountname/sso. Click Continue to be redirected to Duo Single Sign-On to begin authentication.

Active Directory Login

With Active Directory as the Duo SSO authentication source, enter the primary username (email address) on the Duo SSO login page and click or tap Next.

Enter the AD primary password and click or tap Log in to continue.

SAML Login

With another SAML identity provider as the Duo SSO authentication source, Duo SSO immediately redirects the login attempt to that SAML IdP for primary authentication. Users do not see the Duo SSO primary login screen.

Duo Authentication

Successful verification of your primary credentials by Active Directory or a SAML IdP redirects back to Duo. Complete Duo two-factor authentication when prompted and then you'll return to GitHub Enterprise to complete the login process.

*Universal Prompt experience shown.

You can also log into GitHub Enterprise using Duo Central, our cloud-hosted portal which allows users to access all of their applications in one spot. Link to GitHub Enterprise in Duo Central by adding it as an application tile. Once the tile has been added, log into Duo Central and click the tile for IdP-initiated authentication to GitHub Enterprise.

Congratulations! Your GitHub Enterprise users now authenticate using Duo Single Sign-On.

See the full user login experience, including expired password reset (available for Active Directory authentication sources) in the Duo End User Guide for SSO.

Enable Remembered Devices

To minimize additional Duo two-factor prompts when switching between GitHub Enterprise and your other Duo Single Sign-On SAML applications, be sure to apply a shared "Remembered Devices" policy to your SAML applications.

Troubleshooting

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