When connecting to SAML-protected URLs, Host Checker is installed if used on the realm

Pulse is managed via non-browser connections; however, the browser-based Host Checker is showing as installed. This article explains what causes this and that the program is working as designed.

Host Checker is showing as a separately installed application; however, all deployment is controlled external to a browser and is not expected to be present.

When a realm is configured for SAML authentication, a browser instance is created by Junos Pulse to handle the redirects required to complete the authentication/authorization sequence. If a realm is configured for Host Checker, the browser-accessible client will be installed in order to provide compliance checking and updates during login.

 

About the author

James Palmer

Leave a Comment