The workaround doesn't seem to be viable as the impact of this issue is felt already and it's not possible for us to know the domain of the captive portal to be added to theUmbrella Proxy Exclusion list in advance.
We typically receive reports of connection issues while a user is traveling with their SWG protected laptop, and they're attempting to connect to a Captive Portal enabled Wi-Fi network at their hotel, for example.
At this point we're having to disable the SWG module for their device from the dashboard.
Is there anyone else facing this issue?
What else can be done to mitigate the impact of this issue?
