Using TLS/SSL with the Voting Service - Agenda Voting - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Essential - Premier - Standard

Agenda Voting

Agenda Voting
Foundation 23.1

Typically, the messages sent and received between OnBase Minutes and the Voting Client and Voting Client Display are in plain text, when not using TLS/SSL. You can securely configure the connection between the service and each Client application using TLS/SSL by doing the following:

  1. Locate the hash or thumbprint of your certificate. This is found on the Details tab of the certificate, and is typically located by scrolling down to the bottom of the list.

    The hash/thumbprint can be copied from here, but be aware that to use this value, the spaces between the character pairs need to be removed.

  2. Open a command prompt as an administrator.
  3. Run one of the following command lines after inserting the hash/thumbprint:
    • netsh http add sslcert ipport= certhash=[insert hash/thumbprint value here] appid={acbeef11-b84f-4fe3-8359-ca6c28b107dc}

    • netsh http add sslcert hostnameport=[server name here]:8080 certhash=[hash/thumbprint value here] appid={acbeef11-b84f-4fe3-8359-ca6c28b107dc} certstorename=MY

  4. In the BoardMeetingService.exe.config file, locate the Hyland.BoardMeeting.Service/Application section and do the following:
    • Ensure that the ServerAddress matches the name of the server in the certificate.

    • Ensure that the AllowInsecureConnections setting is set to false(this is the default value, but only if the Enable TLS check box is selected during the installation).

  5. Start the Hyland Board Meeting Service.
  6. In the config file for each Client application, locate the Hyland.Applications.PushNotification/HostServer section and set the url setting to include https, along with the same server name from the certificate.