The Epic EMP driver must have the ability to read objects and attributes listed in driver subscriber filter in addition to standard Identity Manager driver security requirements
For more information on object synchronization, see Synchronizing Objects in the NetIQ Identity Manager Driver Administration Guide.
Epic’s SOAP interface is accessible over HTTPS. The Epic EMP driver must be able to connect to the Epic SOAP interface over this https connection. Make certain any firewall rules are updated to allow the Epic driver to communicate with Epic (TCP port 443 unless otherwise configured in the Epic implementation).
Audit User in Epic – The identifier of the person who is creating the new User record. Epic generally recommends that this field be left blank, although some implementations will require a value.
Epic Client ID – Starting with the February 2019 Epic build all API calls must have a Client ID. There are options on how to implement this; the Epic Driver is using the http header option.
For more information, see Activating the Driver.
Trust all Certs – Though it is not recommended, if the Epic system is utilizing a self-signed certificate, the “Trust All Certs” driver configuration may be enabled (there are security risks associated with utilizing this functionality as it can potentially open the system to MIM attacks).