Disable the Desktop Host "Discovery" Process in the Web Client

[MikeBruckner]

I'm currently working on our upgrade to OnBase 22.1, and was curious to see if anyone has found a way to disable the Desktop Host "discovery" process within the web client? 

For reference, the "discovery" process I'm referring to here is that upon logging into the web client, the user's browser will search for the desktop host by making a handful of calls to http[://]127.0.0.1/discovery (stopping early if the Desktop Host is actually installed and running).

This approach isn't dissimilar from other apps that have similar desktop host integrations, however, within our environment, when these calls are made, the Content Security Policy that we have configured on our web server blocks them. This effectively means that every time a user logs into the web client, we get 11 Content Security Policy violation reports.

We could of course add a CSP directive to allow these calls (for those in a similar position who ARE using the desktop host and have a Content Security Policy set, the directive you would need to add is: connect-src http://127.0.0.1:*/discovery), however, as a security best practice, I'd like to avoid adding anything to our CSP that we know is not (technically) needed within our environment at this time - if at all possible.

Thanks!
-Mike

[Avinash_Mittapa]

Hi @Adam Shane 

I verified desktop host service and printer spooler service are running and we removed load services on start up line to be able to start desktop host service and while we try to launch web client after a workstation reboot, we still get same error and found error in console from browser developer tools.

Do we need to modify anything at workstation or network level or desktop host config level to resolve this.

do we have to comment idp part from line 11 to 20 in config file since we dont have idp module.

 

[AdamShaneHyland]

Hi @Avinash Mittapalli ,

You could confirm if you have the Desktop Host Gateway whitelisted within the config.json (i.e. C:\ProgramData\Hyland\DesktopHost\bin).

If this doesn't work, then I would recommend working with your first line of support for further assistance.

Take care.

[Avinash_Mittapa]

Hi @Adam Shane 
Thanks for the inputs!

I added this in whitelist address and able to get rid of no-cors issue, but still getting message while i access web client and console showing discovery error. i added web server ip:8080 and web client url. am i supposed to only have 1287.0.0.1:8080 in whitelist addresses. 

[AdamShaneHyland]

Hi @Avinash Mittapalli ,

You would need to have 127.0.0.1:8080 since the Desktop Host Gateway is running locally.  However, I can't say that you would ONLY need this address for it to work.

Take care.