.svg){kind=logo}
FAQs for Epic Hyperdrive
- 08 May 2024
- 3 Minutes to read
- Contributors
- DarkLight
- PDF
FAQs for Epic Hyperdrive
- Updated on 08 May 2024
- 3 Minutes to read
- Contributors
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
FAQs for Epic Hyperdrive
1) Will both a client and server side update be required of our Epic Plugin?
If you will be using Citrix to serve up Hyperdrive, only a server update will be required. Otherwise, if you will be using Hyperdrive on the client, then a client side update would be required.
2) Will the old version be able to play with the new version, especially on the Hyperspace servers? Meaning, could our current plug-in be on the server and clients pointed to that while other clients may be pointed to the new one, similar to what we had to do in preparation for Epic 2018?
The new version that supports Hyperdrive will be separate from the current version that supports Hyperspace (meaning the new version will have a separate install). The current and new versions will be able to coexist on the same computer. Epic E0G records can be modified to support both versions installed on the same machine. Please reach out to your Epic TS to change the login device configuration using the following ProgIDs.
Note
IA.Hyperdrive.ProxCardPassive is only supported in the Narrator workflow. Use Epic's documentation for the context in which this should be configured. In addition, this device requires that the IA.Hyperdrive.ProxCard device has been configured for primary authentication. You only need to configure the passive/secondary auth E0G record if your organization is currently using our integration for these workflows.
ProgIDs for prior Hyperspace version:
HCILoginDeviceNET.ProxCard and HCILoginDeviceNET.ProxCardPassive
ProgIDs for Hyperdrive:
IA.Hyperdrive.ProxCard and IA.Hyperdrive.ProxCardPassive.
3) What version(s) of XA will support Hyperdrive? For example, will we support XA v4.12.5 working with Auth Plugin 4.0.0?
Because the change to using Hyperdrive does not require any specific XA changes, the new versions of the Epic Auth plugin should work with any XA version that is currently being used with the latest GA release of our Epic Auth plugin. However, we recommend updating to XA 4.12 or above to avoid the possibility of finding issues with an older version that would then need to be upgraded to the supported versions.
4) What would happen if some users needed to get to Hyperdrive on a device by default but also needed to get back to Hyperspace in the transition?
You could run either Hyperspace or Hyperdrive as needed. However, your Epic configuration would also need to be changed to use the appropriate ProgID for the plugin you want to use. You can have both plugins listed in Epic's Authentication Administration for the same E0G record, and the client app (HD or HS) will automatically use the correct plugin.
5) If I use WarpDrive to launch Epic Hyperspace today on our SSO workstations, will there be any required changes when migrating to Hyperdrive?
Epic is transitioning away from WarpDrive in favor of using Slingshot (although currently you may use WarpDrive to launch Hyperdrive). EpicAuth will work when using Slingshot as a launcher.
6) What is Identity Automation's recommendation for a smooth rollout of Auth Plug-in knowing we will need to phase the cutover based on Epic's recommendations?
Epic has a progressive cutover recommendation. In general, Identity Automation recommends following this, with preference for a slow initial rollout so as not to introduce unneeded complexity and workload.
7) With the conversion from Hyperspace to Hyperdrive, are there any client side settings that we should expect will change from our current configuration?
The existing client side settings will continue to be used with the v4 Hyperdrive compatible Epic Authentication plugin. One change that may be required is the XA PubLauncher Title setting - If it contains a dash, please remove it.
8) When installing the new Auth Plug-in, is there any specific order of events that should be followed for best practice?
Please see the "Getting Started" section of this document for details.
9) If we are using Identity Automation's E-Prescribing, will a separate update be required?
Yes. Identity Automation's EPCS solution is a separate product and install that has been updated to support Hyperdrive.
10) We are planning on using Citrix App Layering in our Hyperdrive environment. Do you anticipate any issues with your authentication device and Citrix App Layering?
No.
11) Do you support Slingshot launching Hyperdrive but the login device is running locally?
No.
Was this article helpful?