Add two-factor authentication and flexible security policies to GitLab SaaS SAML 2.0 logins with Duo Single-Sign On, our cloud-hosted SSO identity provider, offering inline self-service enrollment and authentication with Duo Universal Prompt.
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.
Duo Single Sign-On is our cloud-hosted SSO product which layers Duo's strong authentication and flexible policy engine on top of GitLab SaaS 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 GitLab SaaS.
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 GitLab SaaS. Duo checks the user, device, and network against an application's policy before allowing access to the application.
Before configuring GitLab SaaS 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 GitLab SaaS application in Duo.
Log on to the Duo Admin Panel and navigate to Applications.
Click Protect an Application and locate the entry for GitLab SaaS 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 GitLab SaaS. See Protecting Applications for more information about protecting applications in Duo and additional application options. You'll need the information on the GitLab SaaS page under Downloads later.
GitLab SaaS uses the Mail attribute when authenticating. We've mapped the <Email Address> bridge attribute to Duo Single Sign-On supported authentication source attributes as follows:
|Bridge Attribute||Active Directory||SAML IdP|
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.
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.
Keep the Duo Admin Panel tab open. You will come back to it later.
The new 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 GitLab SaaS 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. You can activate the Universal Prompt experience for users of new and existing Duo GitLab SaaS applications from the Duo Admin Panel.
Before you activate the Universal Prompt for your application, 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.
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 "New Prompt Ready", with these activation control options:
Enable the Universal Prompt experience by selecting Show new Universal Prompt, and then scrolling to the bottom of the page to click Save.
Once you activate the Universal Prompt, the application's Universal Prompt status shows "Update 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.
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 in-scope for Universal Prompt support. 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.
Log into your GitLab SaaS account as an administrative user.
In the left menu sidebar, click Groups.
The "Groups" page opens. Click your group.
In the left menu sidebar, click Settings. Scroll down the left menu sidebar and click SAML SSO.
Return to the Duo Admin Panel. Under "Metadata", copy the Identity provider single sign-on URL and paste it into the GitLab SaaS Identity provider single sign-on URL field under "Configuration".
Return to the Duo Admin Panel. Under "Certificate Fingerprints", copy the Certificate fingerprint and paste it into the GitLab SaaS Certificate fingerprint field.
In your GitLab SaaS account page, click Save changes.
In the "SAML Single Sign On" section, copy your group name and paste it into the Duo Admin Panel Group Name field under "Service Provider". If your group name is common, a unique number may be automatically added to it. Make sure you include this number with your group name.
Scroll to the bottom of the page and click Save.
Return to your GitLab SaaS account page. Scroll down to the "Configuration" section and click Verify SAML Configuration.
Learn more about GitLab SaaS SSO at GitLab Docs.
You can log on to GitLab SaaS by navigating to your GitLab SaaS SSO page e.g., https://gitlab.com/groups/yourgroup. Click Sign in to be redirected to Duo Single Sign-On to begin authentication.
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.
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.
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 GitLab SaaS to complete the login process.
* Universal Prompt experience shown.
You can also log into GitLab SaaS using Duo Central, our cloud-hosted portal which allows users to access all of their applications in one spot. Link to GitLab SaaS 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 GitLab SaaS.
Congratulations! Your GitLab SaaS users now authenticate using Duo Single Sign-On.
To minimize additional Duo two-factor prompts when switching between GitLab SaaS and your other Duo Single Sign-On SAML applications, be sure to apply a shared "Remembered Devices" policy to your SAML applications.