Skip navigation

Duo Authentication for Epic - FAQ

Last Updated: March 19th, 2021

Duo integrates with Epic Hyperspace to add two-factor authentication to Epic client logins.

What Hyperspace versions does Duo support?

Duo Authentication for Epic is compatible with Hyperspace versions 2010 through the current 2019 release. Contact Epic technical support for assistance configuring Duo in your installed version.

Which Windows versions does Duo Authentication for Epic support?

Duo Authentication for Epic is supported on Windows 8.1 and 10 desktop clients, and Windows Server 2012 and later.

Microsoft ended support for Windows Vista on April 11, 2017, and ended support for Windows 7, 2008, and 2008 R2 on January 14, 2020. Duo no longer supports installation of any Duo applications on these operating systems. We strongly urge you to upgrade to a supported version of Windows.

Does Duo Authentication for Epic protect initial Hyperspace client logons?

No, Duo Authentication for Epic may only be used for workflows that require re-authentication after completing Hyperspace client logon, like EPCS workflows.

Does Duo protect Epic Hyperdrive client logins?

The current Duo 2FA application for Epic supports Hyperspace only. Duo plans to produce a compatible integration for Hyperdrive. Contact your Duo account executive or customer success manager for more information.

Can I configure Duo Authentication for Epic to fail open?

The "fail mode" determines whether users may or may not log into a protected application when the Duo cloud service is unreachable. Duo Authentication for Epic will always "fail closed" if it is unable to contact the Duo service. This means that users can not log on to Epic without successful Duo two-factor authentication. This setting is not configurable.

Why do I receive an error message during EPCS authentication stating that the application does not support unknown users?

The user attempting to authentication with Duo for Epic is not enrolled in Duo with a two-factor device. Duo Authentication for Epic doesn't support inline self-enrollment. Enroll your users in Duo ahead of time using directory synchronization, CSV import, or another enrollment method.

Additionally, Duo Authentication for Epic sends the Epic application username as the Duo username by default. If your users are enrolled in Duo under their Windows usernames (and these do not match the Epic usernames) you can either add your Epic usernames to existing Duo users as username aliases, or use Group Policy to change the "Client: Duo Username Source" setting from the Epic username to the Windows username.

Can I do a scripted install of Duo Authentication for Epic?

Yes, after downloading the msi install file enter the following command into PowerShell or add to a script to silently install Duo for Epic.

cmd.exe /c DuoEpic.msi DUO_IKEY=Integration Key DUO_SKEY=Secret Key DUO_HOST=API Hostname

How do I enable Duo debug logging on a single Epic client without using a group policy object (GPO)?

Perform the following steps on the system where the Epic Hyperspace client and Duo Authentication for Epic are installed.

  1. Close and exit the Epic client.
  2. As an administrator, launch the Registry Editor (regedit.exe).
  3. Navigate to HKLM\Software\Policies\Duo Security\Epic.
  4. Create a new DWORD value named EpicEnableDebugLogging set to 1.
  5. Reopen the Epic client and attempt Duo authentication.
  6. View the resulting debug file "DuoEpic.log" in the current user's %TEMP% directory (e.g. C:\Users\DuoUser\AppData\Local\Temp\DuoEpic.log).

Can I publish the Duo Authentication for Epic to clients using Active Directory?

Yes, the Duo Authentication for Epic client may be deployed via a Group Policy software installation package.

First, create a transform for the installer file by using a table editor tool like Orca. Open the DuoEpic.msi in the editor, click on the Property table, and add these new rows using your Epic application's information from the Duo Admin Panel:

Property Value
DUO_IKEY Your Duo integration key
DUO_SKEY Your Duo secret key
DUO_HOST API hostname

Orca Property Table with Duo rows

Save the transform as an MST file and copy that transform along with the DuoEpic.msi installer to your application deployment repository. The share with the MST file should not be readable by unprivileged user accounts to prevent exposure of the Duo secret key.

In the Group Policy Management console, create a new GPO for Duo Epic publishing. Navigate to Computer Configuration\Policies\Software Settings\Software installation then right-click and select New > Package.

Select the network accessible DuoEpic.msi installer package and choose Advanced as the deployment method. In the properties window go to the Modifications tab. Click the Add button and select the MST transform you created earlier. Click OK to finish, and the Duo Authentication for Epic software package is created.

Here's a sample software publishing policy for Duo Authentication for Epic.

DSoftware Publishing GPO

Learn more about installing software using Group Policy at Microsoft Support.

Additional Troubleshooting

Need more help? Try searching our Epic Knowledge Base articles or Community discussions. For further assistance, contact Support.