Zscaler lockdown exception rules not working as expected
This article describes an issue where Zscaler lockdown exception rules not working as expected.
Problem or Goal
Zscaler lock down exceptions are pushed from the Pulse Connect Secure device to the client, but lock down exception are not accepted by the client.
Behavior: Zscaler App is added an exception rule in the lockdown mode. The app might have connectivity issue.
Cause
This issue occurs, when one of following condition are met:
The exception rules are added only in one direction
Not all processes of Zscaler are added to the exception rule
Solution
Usually all endpoint application have 2-way communication, under Pulse Secure Client > Connections > <Connection Name>, you will need to add exception rules for both inbound and outbound traffic for all Zscaler processes.
Once added, under Pulse Secure Client > Pulse Secure Client Connections, you will select the appropriate connection set and use the 'update client' options to push the modified connection set to the end user's machines.
