Duo Access Gateway will reach end of life in October 2023. Customers may not create new DAG applications after May 19, 2022. Please see the Guide to Duo Access Gateway end of life for more details.
Use the Duo Single Sign-on Generic Service Provider application to protect BlueJeans with Duo Single Sign-On, our cloud-hosted identity provider featuring Duo Central and the Duo Universal Prompt.
If you already use Duo Access Gateway to protect BlueJeans, try the DAG to Duo SSO application migration process.
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 BlueJeans 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 BlueJeans.
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 BlueJeans. Duo checks the user, device, and network against an application's policy before allowing access to the application.
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.
Add the attributes from the table below that correspond to the attributes Mail attribute, Username attribute, Last name attribute, First name attribute, Title attribute, Phone number attribute, and Company 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,givenName,sn,title,telephoneNumber,company in the "Attributes" field.
|First name attribute||givenName||gn|
|Last name attribute||sn||sn|
|Phone Number attribute||telephoneNumber||telephoneNumber|
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 BlueJeans when configuring SSO. Click the Download Certificate link to obtain the token signing certificate (the downloaded file is named "dag.crt").
Add the Duo Access Gateway as a new single sign-on provider for BlueJeans.
Log on to the BlueJeans site as an administrative user and navigate to Admin → Group Settings. Click on the Security tab.
Select SAML Single Sign On under Authentication Options. The page will expand with new options.
If you would like new users to be automatically created upon their first time logging into BlueJeans, check the Enable automatic provisioning box.
The "Certificate Path" is the DAG Metadata certificate supplied by Duo Access Gateway. Click the Choose file button 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 BlueJeans Login URL and Password Change URL fields.
Copy the Logout URL information from the Duo Access Gateway admin console Metadata display and paste it into the BlueJeans Logout URL field.
Leave Custom Error Page URL blank.
Check the Pick User Id from <saml2:NameID> element box.
Fill out the remaining fields with the following information based on the Authentication Source you have configured for your Duo Access Gateway:
|BlueJeans Attribute||Active Directory Attribute||OpenLDAP Attribute||SAML IdP Attribute||Google Attribute||Azure Attribute|
|Phone||telephoneNumber||telephoneNumber||telephoneNumber||Leave Blank||Leave Blank|
|Company||company||physicalDeliveryOfficeName||company||Leave Blank||Leave Blank|
After you've entered all the required information click Save.
Learn more about BlueJeans SSO in the BlueJeans Knowledge Base.
Log on to the Duo Admin Panel and navigate to Applications.
Click Protect an Application and locate the entry for BlueJeans with a protection type of "2FA with SSO self-hosted (Duo Access Gateway)" in the applications list. Click Protect to the far-right to start configuring BlueJeans. See Protecting Applications for more information about protecting applications in Duo and additional application options.
The Domain name is the domain used when logging into your company's BlueJeans site. For example, if your BlueJeans login URL is https://yourdomain.bluejeans.com, enter yourdomain.
BlueJeans 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 BlueJeans application settings (as a JSON file).
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 BlueJeans SAML application JSON file you downloaded from the Duo Admin Panel earlier. Click the Upload button after selecting the JSON configuration file.
The BlueJeans SAML application is added.
You can log on to BlueJeans using your organization’s domain login page e.g. https://yourdomain.bluejeans.com. Clicking the Log In button redirects to the Duo Access Gateway login page. Enter your primary directory logon information, approve Duo two-factor authentication, and get redirected back to the BlueJeans site after authenticating.
If using the BlueJeans mobile app, tap the “Log In” link at the bottom of the login screen, enter your federated e-mail address, and then authenticate to Duo Access Gateway.
Congratulations! Your BlueJeans users now authenticate using Duo Access Gateway.
If you plan to permit use of WebAuthn authentication methods (security keys, U2F tokens, or Touch ID) in the traditional Duo Prompt, Duo recommends configuring allowed hostnames for this application and any others that show the inline Duo Prompt before onboarding your end-users.
The Duo Universal Prompt has built-in protection from unauthorized domains so this setting does not apply.
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 BlueJeans. Learn more about configuring BlueJeans SSO with AD FS at the BlueJeans Knowledge Base.
After you have successfully configured and tested AD FS SSO login to BlueJeans 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 BlueJeans.
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.