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 Single Sign-On, now in public beta, is our cloud-hosted SSO product which layers Duo's strong authentication and flexible policy engine on top of Salesforce logins using the Security Assertion Markup Language (SAML) 2.0 authentication standard. Duo Single Sign-On acts as an identity provider (IdP), authenticating your users using existing on-premises Active Directory (AD) or any SAML 2.0 IdP and prompting for two-factor authentication before permitting access to Salesforce.
Duo Single Sign-On's public beta is available in 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 Salesforce. Duo checks the user, device, and network against an application's policy before allowing access to the application.
Before configuring Salesforce you'll first need to configure Duo Single Sign-On with a working an authentication source.
Log on to the Duo Admin Panel and navigate to Applications.
Click Protect an Application and locate the "Single Sign-On (hosted by Duo)" entry for Salesforce in the applications list. Click Protect to the far-right to start configuring Salesforce. See Protecting Applications for more information about protecting applications in Duo and additional application options. You'll need the information on the Salesforce page under Metadata later.
Salesforce SSO requires a custom domain. If you don't already have a domain for your organization, create one.
Log on to your Salesforce site as an administrator.
If you're using the Salesforce Classic UI, navigate to Domain Management → My Domain. If you're using the Salesforce Lightning Experience UI, navigate to Setup → Settings → Company Settings → My Domain.
Enter a subdomain name, check for availability, and click Register Domain.
When your domain name becomes available, log out and back in as an administrator using your new domain. Navigate back to the "My Domain" page and click the Deploy to Users button.
For more information about creating a custom domain see Salesforce's My Domain help articles.
Add Duo Single Sign-On as a new single sign-on provider in Salesforce.
Log on to your Salesforce site as an administrator.
In the Salesforce Classic UI, navigate to Security Controls → Single Sign-On Settings. In the Salesforce Lightning Experience UI, navigate to Setup → Settings → Identity → Single Sign-On Settings.
Click the Edit button and select the SAML Enabled option. Click Save.
Click the New SAML Single Sign-on Settings button.
Enter a descriptive Name for the SSO configuration. Salesforce uses the name you enter here to populate the API Name.
Copy the Issuer from the Duo Admin Panel Metadata section and paste it into the Salesforce SSO Issuer field.
Enter your Salesforce organization's custom domain (e.g. https://yourorg.my.salesforce.com) into the Entity ID field. Duo also needs the Salesforce domain URL to configure your Salesforce application later.
Click Download certificate next to "Identity Provider Certificate" on the Duo Admin Panel under Downloads to download the Duo Single Sign-On signing certificate. Upload the certiciate to the Identity Provider Certificate section in Salesforce.
Leave the "Request Signing Certificate", "Request Signature Method", "Assertion Decryption Certificate", "SAML Identity Type", and "SAML Identity Location" settings at their default values for now.
Copy the Identity Provider Login URL from the Duo Admin Panel Metadata section and paste it into the Salesforce SSO Identity Provider Login URL field.
Copy the Identity Provider Logout URL from the Duo Admin Panel Metadata section and paste it into the Salesforce SSO Identity Provider Logout URL field.
After you've entered all the required information click the Save button.
Review the SSO details for correctness. Make note of the Entity ID and Login URL as you'll need to provide that information to Duo.
Add your new Duo Single Sign-On provider to your Saleforce login page.
While logged in to the Salesforce admin site as an administrator navigate to Domain Management → My Domain (Salesforce Classic UI) or Setup → Settings → Company Settings → My Domain (Salesforce Lightning Experience UI).
Scroll down to the "Authentication Configuration" section of the "My Domain" page and click Edit.
Check the box for your Duo Single Sign-On SSO configuration in the Authentication Service setting. Click Save.
Return to the Duo Admin Panel with the Salesforce application open. Find the Service Provider section.
Copy the Entity ID from the Salesforce SAML Single Sign-On Setting Detail page and enter it into the Entity ID field in the Duo Admin Panel.
Copy the Login URL from the Salesforce SAML Single Sign-On Setting Detail page and enter it into the Login URL field in the Duo Admin Panel.
Salesforce 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.
Scroll to the bottom of the page and click the Save button.
Navigate to your Salesforce custom domain. The login page for your domain now shows a button for Duo Single Sign-On authentication underneath the traditional username and password entry fields. Clicking the SSO button redirects you to the Duo Single Sign-On login page.
Enter your primary directory logon information, approve Duo two-factor authentication, and get redirected back to the Salesforce site after authenticating.
To log in using the Salesforce mobile app, tap Use Custom Domain. Type your Salesforce custom domain URL https://yourorg.my.salesforce.com), and tap Continue. The app shows the Salesforce login page for your domain, including the button for Duo Single Sign-On authentication underneath the traditional username and password entry fields. Tap the SSO button redirects you to the Duo Signle Sign-On login page. Complete primary and Duo authentication to complete login on the Salesforce app.
Congratulations! Your Salesforce users now authenticate using Duo Single Sign-On.
If you want all users logging in to Salesforce only via Duo Single Sign-On, edit the "Authentication Configuration" for your Salesforce domain and uncheck the Login Page authentication service option. You should also edit "My Domain Settings" and enable the "Prevent login from https://login.salesforce.com" option.
To minimize additional Duo two-factor prompts when switching between Salesforce and your other Duo Single Sign-On SAML applications, be sure to apply a shared "Remembered Devices" policy to your SAML applications.
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 Salesforce. Learn more about configuring Salesforce SSO with AD FS at the Salesforce Developer Wiki.
After you have successfully configured and tested AD FS SSO login to Salesforce 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 Salesforce.
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.