Has anyone encountered an issue where when upgrading to DLP 220.127.116.11 where Chrome stopped working propeprly? Specificaly, where have a closed network where credentials to certain sites are no longer accepted. The site keeps prompting for username/password even after it's entered. I'm not convinced that this is a DLP issued but coincidently this happeded after the upgrade. Any thoughts?
If the issue is reproducible on any machine, then it has to be investigated. What was the earlier version of DLP and Chrome version? Are we able to reproduce the issue if under Windows Client Configuration policy-->Operational Modules and Mode-->we un-check Chrome module.
Did you check after removing DLP 11.1 and reinstalling it?
The issued has been reproduced on other machines. The earlier version was 10.x the version of Chrome (62.x) did not change during the upgrade of DLP. Our systems admin roll backed to a previous image with version 10 and there was no issue
Our admins found that from DLP10 HTTP2 was disabled in a sense. With the upgrade to DLP11. HTTP2 had been re-enabled which broke the web app authentication that we were using. The fix was that they manuipulated Chrome to manually disable HTTP2. My question is does un-checking the Operational Modules and Mode for Chrome as you mentioned fixe this issue? Thanks
Disabling the Chrome module means we will no longer monitor uploads while browsing internet using Chrome. So it is just a troubleshooting step not a solution.
I am not aware of any such issues. Would be good if a SR# can be logged for complete troubleshooting.