SATC replacement - Server Endpoint

has anyone experienced intermittent issues since deploying this?
I've installed the Server Protection EAP, ran the powershell to migrate the SATC ini settings to the registry, installed the old SATC and rebooted, and all was working fine. 
but intermittently users get (on chrome) a page to say 'the information you're about to submit is not secure' and clicking 'send anyway' loads up the Sophos window to entering credential to authenticate.

Not too long after, it seems to fix itself.

Thanks

has anyone experienced intermittent issues since deploying this?
I've installed the Server Protection EAP, ran the powershell to migrate the SATC ini settings to the registry, installed the old SATC and rebooted, and all was working fine. 
but intermittently users get (on chrome) a page to say 'the information you're about to submit is not secure' and clicking 'send anyway' loads up the Sophos window to entering credential to authenticate.

Not too long after, it seems to fix itself.

Thanks

Do you have "Show captive Portal to unknown user" in the firewall active? Try to disable this. 

Hi, we do have that active. We have always had that active even with the old SATC. Would disabling this help with the issue / is it a known problem with the new SATC built into server protection EAP? Most of the time is does work fine, but intermittently it does stop working and then loads  'the information you're about to submit is not secure' chrome error. 

cheers

I would recommend to disable this and check again. It looks like the captive Portal, which cannot work for this portal. 

Just had a user report the issue and I disabled the captive portal and it instantly fixed it - looking promising! Thank you

I'm not sure it's quite that simple. What's probably happening is there is a short period of time before the authentication request gets passed via heartbeat.

So by disabling the captive portal prompt all you're doing is then letting the user browse unauthenticated (via whatever associated policy) until the auth request gets passed, in my experience anything up to 120 seconds. So not a show stopper, but worth being aware of.

I'm happy to be corrected.