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.
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 Access Gateway (DAG), our on-premises SSO product, layers Duo's strong authentication and flexible policy engine on top of ShareFile 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 ShareFile.
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 ShareFile. 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 ShareFile 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 ShareFile.
Log on to ShareFile as an administrative user and navigate to Settings → Admin Settings → Security → Login & Security Policy.
Once on the "Login & Security Policy" page scroll down to "Single sign-on / SAML 2.0 Configuration " and check the Enable SAML option under "Basic Settings".
Enter your organization's ShareFile login URL as the ShareFile Issuer / Entity ID. For example, if your ShareFile subdomain is yourdomain.sharefile.com enter https://yourdomain.sharefile.com/saml/info.
Copy the Entity ID information from the Duo Access Gateway admin console Metadata display and paste it into the ShareFile Identity IDP Issuer / Entity ID field.
The "X.509 Certificate" is the DAG Metadata certificate supplied by Duo Access Gateway. Open the dag.crt file in a text editor (like Notepad), and copy the entire contents of the file (including the
-----BEGIN CERTIFICATE----- and
-----END CERTIFICATE----- lines). Paste the certificate file text into this field.
Copy the SSO URL information from the Duo Access Gateway admin console Metadata display and paste it into the ShareFile Login URL field.
Copy the Logout URL information from the Duo Access Gateway admin console Metadata display and paste it into the ShareFile Logout URL field.
Select Yes next to Enable Web Authentication under "Optional Settings". You can also review the additional options.
After you've entered all the required information click Save.
Learn more about ShareFile SSO at the ShareFile support site.
Log on to the Duo Admin Panel and navigate to Applications.
Click Protect an Application and locate the entry for ShareFile 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 ShareFile. See Protecting Applications for more information about protecting applications in Duo and additional application options.
The Subdomain name is the subdomain used when logging into your organization's ShareFile account. For example, if your ShareFile login URL is yourdomain.sharefile.com then enter yourdomain as the subdomain name in Duo.
Note: The subdomain name is case sensitive and should appear exactly as you've configured it in ShareFile.
The DAG Entity ID is the information from the Duo Access Gateway admin console Metadata Entity ID display field.
ShareFile 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 ShareFile 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 ShareFile SAML application JSON file you downloaded from the Duo Admin Panel earlier. Click the Upload button after selecting the JSON configuration file.
The ShareFile SAML application is added.
You can log on to ShareFile by navigating to your ShareFile SSO page e.g. https://yourdomain.sharefile.com/saml/login. This 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 ShareFile site after authenticating.
Congratulations! Your ShareFile users now authenticate using Duo Access Gateway.
To minimize additional Duo two-factor prompts when switching between ShareFile and your other Duo Access Gateway SAML applications, be sure to apply a shared "Remembered Devices" policy to your SAML applications. See the Duo Access Gateway with Remembered Devices instructions.
You can require that all users sign into ShareFile using the Duo Access Gateway.
Return to ShareFile as an administrative user and navigate to the SAML settings.
Select Yes next to Require SSO Login under "Optional Settings".
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.