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 Remedyforce 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 Remedyforce, 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 Remedyforce 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 Active Directory (AD) or LDAP credentials and prompting for two-factor authentication before permitting access to Remedyforce.
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 Remedyforce. 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 Duo attributes Mail attribute and Username 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 in the "Attributes" field.
|Duo Attribute||Active Directory||OpenLDAP|
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 Remedyforce when configuring SSO. Click the Download Certificate link to obtain the token signing certificate (the downloaded file is named "dag.crt").
Remedyforce SSO requires a custom domain. If you don't already have a domain for your organization, create one.
Log on to your Remedyforce 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 Remedyforce's My Domain help articles.
Add the Duo Access Gateway as a new single sign-on provider in Remedyforce.
Log on to your Remedyforce 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. Select the SAML Enabled option and the Make Federation ID case-insensitive option. Click Save.
Click the New SAML Single Sign-on Settings button.
Enter a descriptive Name for the SSO configuration. Remedyforce uses the name you enter here to populate the API Name.
Copy the Entity ID URL from the Duo Access Gateway admin console metadata display and paste it into the Remedyforce SSO Issuer field.
Enter your Remedyforce organization's custom domain (e.g. https://yourorg.my.salesforce.com) into the Entity ID field. Duo also needs the Remedyforce domain URL to create your Remedyforce application in the next section.
The "Identity Provider Certificate" is the DAG Metadata certificate supplied by Duo Access Gateway. Click the Browse button to select the dag.crt file you downloaded from the DAG admin console Application page earlier. Upload the certificate.
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 SSO URL information from the Duo Access Gateway admin console Metadata display and paste it into the Remedyforce SSO Identity Provider Login URL field.
Copy the Logout URL information from the Duo Access Gateway admin console Metadata display and paste it into the Remedyforce SSO Identity Provider Logout URL field.
Change the "Service Provider Initiated Request Binding" setting to HTTP Redirect. If the only available option is "HTTP POST" then you must create and deploy a custom domain as shown in Remedyforce Custom Domain Requirement.
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 Salesforce Login URL as you'll need to provide that information to Duo.
Add your new Duo Access Gateway SSO provider to your Salesforce login page.
While logged in to the Remedyforce 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 Access Gateway SSO configuration in the Authentication Service setting. Click Save.
Log on to the Duo Admin Panel and navigate to Applications.
Click Protect an Application and locate the entry for Remedyforce 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 Remedyforce. See Protecting Applications for more information about protecting applications in Duo and additional application options.
Copy the Entity ID from the Remedyforce SAML Single Sign-On Setting Detail page and enter it into the Entity ID field in the Duo Admin Panel.
Copy the Salesforce Login URL from the Remedyforce SAML Single Sign-On Setting Detail page and enter it into the Login URL field in the Duo Admin Panel.
Remedyforce 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 Remedyforce 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 Remedyforce SAML application JSON file you downloaded from the Duo Admin Panel earlier. Click the Upload button after selecting the JSON configuration file.
The Remedyforce SAML application is added.
Navigate to your Remedyforce custom domain. The login page for your domain now shows a button for DAG SSO authentication underneath the traditional username and password entry fields. Clicking the SSO button redirects you to the Duo Access Gateway login page.
Enter your primary directory logon information, approve Duo two-factor authentication, and get redirected back to the Remedyforce site after authenticating.
To log in using the Salesforce1 mobile app, click the app menu and select Change Server. Select your custom domain from the list (or click Add Connection and add your Remedyforce custom domain URL https://yourorg.my.salesforce.com), and click Apply. The app shows the Remedyforce login page for your domain, including the button for DAG SSO authentication underneath the traditional username and password entry fields. Clicking the SSO button redirects you to the Duo Access Gateway login page. Complete primary and Duo authentication to complete login on the Remedyforce1 app.
Congratulations! Your Remedyforce 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.
If you want all users logging in to Remedyforce only via Duo Access Gateway, edit the Authentication Configuration for your Remedyforce domain and uncheck the "Login Page" authentication service option.
Refer to the Salesforce article Configuring SAML Settings for Single Sign-On for additional information.
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 Remedyforce. Learn more about configuring Remedyforce SSO with AD FS at the Salesforce Developer Wiki.
After you have successfully configured and tested AD FS SSO login to Remedyforce 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 Remedyforce.
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.