Infeasible
Status Update
No update yet.
Comments
ra...@google.com Restricted+
Restricted+
Comment has been deleted.
ra...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
- As you have mentioned that this issue is happening on chrome os. Could you please confirm this issue is also happening in android os as well. If yes, please share a bugreport.
- Please confirm if this is your android app :https://play.google.com/store/apps/details?id=zscaler.com.zscaler&hl=en_IN
- As you have mentioned that this issue is happening on chrome os. Could you please confirm this issue is also happening in android os as well. If yes, please share a bugreport.
- Please confirm if this is your android app :
ra...@google.com
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report to google drive and share the folder to android-bugreport@google.com, then share the link here.
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report to google drive and share the folder to android-bugreport@google.com, then share the link here.
br...@zscaler.com
this issue is specific to chroemOS.
ra...@google.com
Thanks for the information. We are closing this issue as it is related to chromeOS.
This forum is for reporting Android issues only. If you have a bug that can be reproduced on a Nexus or Pixel device, we'd be pleased to investigate it. Thanks
br...@zscaler.com
Raised a new public ticket in chromeOS to handle it (
Description
We are providing Zscaler Client connector solution with always on vpn so that they could get the touchless auth and then enforcement of the vpn 24x7 on their chromeoOS .
However, recently we have seen few issues with the zscaler package, where the package being enforced with "always on vpn" being installed on the chromeOS , kicks in the always on vpn and then app latches on the event and starts its functionality internally.
However, there was an issue raised recently by customer, where even after chromeOS login, the always on VPN did not kick in. Although in the previous login, the ZCC was installed, enforeced AOV, and then ZCC logged in too. However, successive login to chromeOS, we dont see the AOV launching at all , until ZCC was brought up.
Please refer to the video for reference.
Bug reports include personal information logged on your device or by apps, such as:
File names : Logs are located including ZCC logs, and System logs altogether :
Timeline for events :
{{ CB TIME EVENT }}
------ -------------------------------------------------
10:29 Guns.com loads - Not blocked
10:30 google search for worldstarhiphop
10:31 Wordstar.com loads
10:32 Opens Up ZCC - "loading it may take a few minutes"
10:33 ZCC opens up 10:33 - ZCC Shows Service Status OFF
10:33 ZCC shows Service Status "Connecting" 10:33 - ZCC shows Servive status "Authentication Error"
Installed apps and usage: zscaler.com.doetestdec09
Not sure what is stopping the chromeOS to not launch the AOV on successive login to chromeOS, which is affecting the critical customer to secure their network.