Configuring HTTPSAutomation - Application Enabler - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

Application Enabler

Platform
OnBase
Product
Application Enabler
Release
Foundation 23.1
License
Standard
Essential
Premier
Note:

Enabling HTTPSAutomation allows the use of the HTTPS protocol when automating Application Enabler. It does not change the security of your enabled application.

The following requirements need to be configured prior to enabling HTTPSAutomation:

  • A domain which 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 HTTPSAutomation (e.g. distributed to every workstation, or stored in a network share accessible via UNC).

If your solution does not require a unique domain, localhost.onbase.com can be used.

A certificate for the localhost.onbase.com domain can be obtained by contacting your first line of support.

To allow scrape XML to post to Application Enabler using an HTTPS binding, complete the following steps:

  1. Ensure that service mode is enabled in the Unity Client .config file.
  2. Ensure that Application Enabler is enabled in the Unity Client .config file.
  3. In the Unity Client .config file, locate the Hyland.Canvas.Automation.Services element. Ensure that HttpsAutomation is enabled.
    By default, port 15425 is used for sending the HTTPS POST request. If necessary, you can change the port value to a different open port on the local machine where Application Enabler is installed.
  4. In the HttpsAutomation element, for the certificateLocation value, enter the location of the certificate.

    If the certificate is stored in a network share, the value of certificateLocation would be the UNC path the certificate. If the certificate is distributed to every workstation, the value of certificateLocation can be an absolute or relative path to the certificate.

    For example, if the certificate is stored in the same location where Application Enabler is installed, the value of certificateLocation can be the file name of the certificate.