KNOWLEDGE BASE ARTICLE

Using Umango TWAIN Scanning When HTTPS Is Enabled

Umango uses a web socket to communicate with the Umango Scan Actuator when connecting to TWAIN scanners. When https is enabled on your Umango server you will need to create a security exception in the browsers of any client workstations that plan to use TWAIN scanning. This is because the web socket connection to localhost will be secure (wss://) but will be using a self-signed certificate and this typically causes a potential security threat to be reported in your browser. Without creating an exception, your browser will block communication to the Scan Actuator.

If your network administrator understands this and has agreed that this configuration does not pose a security threat within your environment, you can proceed to create a security exception. To create the exceptions, follow the steps below on each of the client workstations that will be using TWAIN to scan:

1. Ensure your Umango server has https enabled and working
2. Ensure your Umango Scan Actuator is installed and has a localhost self signed certificate assigned and functioning
3. Open your browser on the client computer (the example below is using Microsoft Edge)
4. In your browser's address bar, enter the address below and press enter (changing out the port if you have set it to a non-default port)
   https://localhost:50082
5. You will then see a warning like the one below:
   
6. Press the "Advanced" button.
   
7. Press the link to "Continue to localhost (unsafe)"
    
8. Although the resulting screen appears to say the site is not working, this is because it is requesting traffic via https but we will be using the wss protocol for web socket traffic.
9. You should now be able to use TWAIN scanning

For information on configuring your x509 certificate on your server and the local workstations (Scan Actuators), read the relevant knowledge articles on these topics.

Link to this article http://umango.com/KB?article=136