If you are installing Application Enabler and you want to expose an HTTPS endpoint to allow third-party applications to perform Application Enabler context events, additional requirements must be met.
The following requirements must be configured prior to enabling HTTPS Automation:
-
A domain that will resolve to localhost.
-
An HTTPS binding public/private key pair for the domain, in .PFX format, that must be trusted by all client workstations.
-
The password for the private key must be OnBase.
-
The key pair must be stored somewhere accessible to all clients using HTTPS Automation (for example, distributed to every workstation or stored in a network share accessible via UNC).
If you need a URL and certificate to use with an HTTPS binding, contact your first line of support.