- #Ocf epic hyperspace how to
- #Ocf epic hyperspace install
- #Ocf epic hyperspace for android
- #Ocf epic hyperspace verification
The security of your Duo application is tied to the security of your secret key (skey).
#Ocf epic hyperspace how to
First Stepsīefore moving on to the deployment steps, it's a good idea to familiarize yourself with Duo administration concepts and features like options for applications, available methods for enrolling Duo users, and Duo policy settings and how to apply them. This application supports Windows 8.1 and later client operating systems, and Windows 2012 and later server operating systems. PrerequisitesĬheck your Windows version before starting.
#Ocf epic hyperspace install
If you're delivering the Epic client via application virtualization (like Citrix XenApp or Microsoft Remote Desktop Services), you should install Duo Authentication for Epic at the application host - not the end-user workstation. The defined Epic application workflow determines the next action. If Duo Authentication for Epic is unable to contact the Duo Security cloud service then Duo "fails closed" and reports the failure to Epic Hyperspace. If your organization requires IP-based rules, please review this Duo KB article. Firewall configurations that restrict outbound access to Duo's service with rules using destination IP addresses or IP address ranges aren't recommended, since these may change over time to maintain our service's high availability. This application communicates with Duo's service on TCP port 443. Consider preventing your Help Desk admins from creating bypass codes for users. No - Do not issue bypass codes to EPCS users. No - Disable SMS use with an Authentication Methods policy No - Disable BlackBerry use with an Operating System policy Yes with Duo Mobile for Windows Phone 2.0 and later
#Ocf epic hyperspace for android
Yes with Duo Mobile for Android 3.25.0 and later Meets EPCS compliance for FIPS 140-2 Level 1?
For the purpose of EPCS compliance, choose between available authentication methods (OTP, Duo Push, phone call, or hardware token) that meet your compliance team’s interpretation of the Federal EPCS Guidelines. One-time passcodes (OTP) are validated to meet FIPS 140-2 Level 1 per the table below.
Read the enrollment documentation to learn more about these options. You'll need to enroll your users ahead of time using directory synchronization, CSV import, or another method.
#Ocf epic hyperspace verification
If configured as a "Passive authentication device", or to authenticate "Patient" logons, the Duo device will report an error message and return a failure to Epic.ĭuo Authentication for Epic does not support inline self-enrollment, as Duo Security is not a qualified credential service provider (CSP) or certificate authority (CA) for EPCS identity verification purposes. In Epic Hyperspace terms, Duo Authentication for Epic is a "Direct authentication device capable of "User" authentication only. NET Framework 4, Windows Installer 4.0 or later, and the Epic Hyperspace client installed on the local system to function none of which are included with the Duo Epic installer. It must be installed on all Epic workstations to provide complete protection. NET component that provides two-factor authentication for Epic Hyperspace 2010 and later (up to and including Hyperspace 2020). Overviewĭuo Authentication for Epic is a client-side. Duo integrates with Epic Hyperspace to add two-factor authentication to Epic Hyperspace e-Prescription workflows.
0 kommentar(er)
