{"version":"https:\/\/jsonfeed.org\/version\/1","title":"Using Docman 10 With a Proxy Server > Docman Help","home_page_url":"https:\/\/help.docman.com\/knowledge-base\/using-docman-10-with-a-proxy-server\/","feed_url":"https:\/\/help.docman.com\/knowledge-base\/using-docman-10-with-a-proxy-server\/feed\/json","author":{"name":"nextSTL","url":"https:\/\/help.docman.com"},"items":[{"title":"Using Docman 10 With a Proxy Server","date_published":"2017-12-12T11:55:45Z","date_modified":"2020-09-11T15:29:19Z","id":"https:\/\/help.docman.com\/knowledge-base\/using-docman-10-with-a-proxy-server\/","url":"https:\/\/help.docman.com\/knowledge-base\/using-docman-10-with-a-proxy-server\/","author":{"name":"Oliver Edwards","url":"","avatar":"https:\/\/secure.gravatar.com\/avatar\/916760a3861c94b0f12d9658070815ac6150c9ba5291c9b5304733d70e0fdb9e?s=96&d=mm&r=g"},"summary":"The Docman 10 Web App utilises SignalR technology to communicate with the Docman Desktop App. This is required to integrate with EMIS, Interact with Scanners, Printers and most importantly automatically update the Docman Desktop App when new versions\u2026","content_html":"The Docman 10 Web App utilises SignalR technology to communicate with the Docman Desktop App. This is required to integrate with EMIS, Interact with Scanners, Printers and most importantly automatically update the Docman Desktop App when new versions are released.\n\nIf your environment has a proxy this will more often than not only allow authenticated traffic through for white listed URLs. If this is the case the Docman 10 Web Application won't be able to communicate\u00a0 with Docman Desktop App\u00a0 in either direction which will result in Docman 10 Web Application displaying a yellow Desktop App connection icon to the right of the search bar as shown below. To resolve this you will need to adjust your proxy configuration script or amend the web filtering in IE.\n\n\"\"<\/a>\n

Configuration Script Exceptions<\/h3>\n\"\"<\/a>\n\nIf you are setting the Automatic Configuration settings in Internet Options to use a configuration script then you should include the below rules in your DAT\/PAC file to ensure the URLs aren't being blocked for authenticated traffic.\n\nif (dnsDomainIs(host, \"dts.docman10.com\")){ return \"DIRECT\"; } if (dnsDomainIs(host, \"*.docman.thirdparty.nhs.uk\")){ return \"DIRECT\"; } if (dnsDomainIs(host, \"*.docman.blob.core.windows.net\")){ return \"DIRECT\"; } if (dnsDomainIs(host, \"*.snow.pctisolutions.co.uk\")){ return \"DIRECT\"; }\n

Proxy Server IE Configuration\"\"<\/a><\/h3>\nWhen using the web filter configuration within IE the configuration below is required.\n\n*.docman10.com; *.snow.pctisolutions.co.uk; *.docman.thirdparty.nhs.uk; *.docman.blob.core.windows.net; *.docman.com;<\/strong>\n

Expected Outcome<\/h3>\nThe dts.docman10.com url is internet facing and is used by the Desktop App to resolve 127.0.0.1. Doing an NSLOOKUP dts.docman10.com will resolve to 127.0.0.1 as shown below. However you can't browse to this url.\n\n\"\"<\/a>\n\nThe *.docman.thirdparty.nhs.uk url can be tested by accessing docman.thirdparty.nhs.uk with an N3 facing connection. This will resolve to the Docman 10 login page.\n\n\"\"<\/a>\n\nThe\u00a0docman.blob.core.windows.net is an internet facing url and resolves to an XML page. When used by the Desktop App Service it will download updates from this location so EXE's, MSI's, and JSON files should be white listed to ensure the files can be downloaded. Unless you are accessing it unauthenticated through your proxy this won't be an accurate test, as the Desktop App Service uses the windows system account to access the docman.blob.core.windows.net url.\n\n\"\"<\/a>\n\nThe snow.pctisolutions.co.uk is an api endpoint so doesn't have a resolvable url.\u00a0\u00a0Unless you are accessing it unauthenticated through your proxy this won't be an accurate test, as the Desktop App Service uses the windows system account to access the\u00a0snow.pctisolutions.co.uk.","tags":[]}]}