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 DigiCert 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 DigiCert.
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 DigiCert. Duo checks the user, device, and network against an application's policy before allowing access to the application.
Add the attribute from the table below that corresponds to the Duo Mail attribute in the "Attributes" field when configuring your Active Directory or OpenLDAP authentication source in the DAG admin console. For example, if Active Directory is your authentication source, enter mail in the "Attributes" field.
|Duo Attribute||Active Directory||OpenLDAP|
If your organization uses another directory attribute than the ones listed here then enter that attribute name 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 DigiCert when configuring SSO.
DigiCert SSO is only available for CertCentral accounts. Please contact DigiCert support at email@example.com to have SSO enabled for your account.
Continue with configuration once DigiCert enables SSO for your account.
Add the Duo Access Gateway as a new single sign-on provider for DigiCert.
Log into DigiCert as an administrative user.
On the left-hand navigation menu select Settings and then select Single Sign-On.
On the "Single Sign-on (SSO)" page click Edit Federation Settings.
On the "Federation Settings" page under "How will you send data from your IDP?" select Use a dynamic URL. A new text field will appear.
Copy the Entity ID URL from the Duo Access Gateway admin console metadata display and paste it into the DigiCert Use a dynamic URL field.
Select NameID for "How will you identify a user?".
Type a unique name that will be used as part of your DigiCert login URL under "Federation Name".
Once you've entered all required information click Save & Finish.
The page will reload and ask you to test an SSO authentication to continue.
Learn more about DigiCert SSO at the DigiCert Support Center.
Log on to the Duo Admin Panel and navigate to Applications.
Click Protect an Application, locate SAML - DigiCert in the applications list, and click Protect this Application. See Getting Started for help.
DigiCert 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 DigiCert 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 DigiCert SAML application JSON file you downloaded from the Duo Admin Panel earlier. Click the Upload button after selecting the JSON configuration file.
The DigiCert SAML application is added.
If your organization enabled the Duo Access Gateway portal, log into the portal page using the link provided by your administrator. Click DigiCert from the dashboard to access the application.
You can log on to DigiCert via Duo Access Gateway using the Login URL provided by the DAG server when you created the DigiCert application in the DAG admin console (https://yourserver.example.com/dag/saml2/idp/SSOService.php?spentityid=https://www.digicert.com/account/sso/metadata).
Congratulations! Your DigiCert users now authenticate using Duo Access Gateway.
By default DigiCert will allow you to sign in either with your username and password or SSO. You can modify this setting to mandate SSO for logging into DigiCert per user.
While logged into DigiCert as an administrative user select Account on the left-hand navigation menu and then select Users.
Click on the name of a user you'd like to enforce SSO for their login.
On the user page under the "User Access" section check the box next to Only allow this user to log in through SAML SSO.
Click Update User.
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 DigiCert. Learn more about configuring DigiCert SSO with AD FS at the DigiCert Support Center site.
After you have successfully configured and tested AD FS SSO login to DigiCert 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 DigiCert.
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.