Content Management and Capture

Content Management and Capture

Come for answers. Stay for best practices. All we’re missing is you.

 View Only

  • 1.  Datacap dynamsoft configuration.

    Posted Mon April 26, 2021 07:11 AM
    Hi , 
    I When I am trying to run datacap (9.1.8) application (in navigator) .In chrome / firefox i am getting following errors (Works in IE)

    1) Firefox (V72) - Content Security Policy: The page's settings blocked the loading of a resource at wss://127.0.0.1:18623/ ("default-src").
    -----------------------------------------------------------
    2) chrome (V90.0.4430.85) - (console) dynamsoft.webtwain.initiate.js:15 Refused to connect to 'wss://127.0.0.1:18623/' because it violates the following Content Security Policy directive: "default-src 'self' blob: https:". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback.
    ----------------------------------------------------------
    3) Torch (V69.2) - The Web TWAIN Module was downloaded successfully!
    dynamsoft.webtwain.initiate.js:13 POST https://127.0.0.1:18621/f/VersionInfo?ts=1619329023710 net::ERR_CONNECTION_REFUSED
    AND it says
    Please download and install the scan module manually.
    *The automatic installation of the module failed

    Which i have few times but still keep getting.
    ---------------------------------------------------------

    How can i make scan module work properly and fix this Content Security Policy issue ?
    Many thanks in return :) .


    ------------------------------
    Arch A
    ------------------------------


  • 2.  RE: Datacap dynamsoft configuration.

    Posted Thu May 13, 2021 01:20 PM
      |   view attached
    Arch A,
    I ran your post past the Datacap team and I got this reply, which is a good start:

    "Yes, I have seen this error before, it happens when users need to configure the Content Security Policy header in Datacap Navigator application. Datacap development released the following document that explains how to configure the "Content Security Policy" on the ICN side to resolve the issue. Please follow the directions in the attached pdf. If it does not resolve then, please open a case to engage ICN L3/L2 support. Please mention in the case that 'Paula' is aware of this request and so request a fast track to engineering. "

    See attachment.

    ------------------------------
    DAVID Jenness
    ------------------------------

    Attachment(s)

    pdf
    Content Security Policy Configuration.pdf   529 KB 1 version
    Original Message