At least you got a heads-up. Few months back GCP "Agent Studio - Build" failed compiling the code in sandbox with a vague error message. Spent weeks troubleshooting, spoke to google engineers and reps, sending code, step by steps, screenshots. No one had a clue, until I switched from Firefox to Chrome out of desperation and it worked without a hitch.
Google workspace threatening to block Firefox access
21–30 of 194 posts
Re: Google workspace threatening to block Firefox access
#22Is it not: https://knowledge.workspace.google.com/admin/security/create... The Org admin can put all sorts of restrictions on who can do what based on the client device setup.
Why is there a policy to require “Chrome” and not a policy to require another browser, hmm?
Re: Google workspace threatening to block Firefox access
#23Seems like a monopolistic move.
Google doesn’t have a monopoly in workspace applications.
Re: Google workspace threatening to block Firefox access
#24Re: Google workspace threatening to block Firefox access
#25This is not a Google-wide thing… this is from Google’s Context-Aware Access product, which is configurable in Google Workspace environments. OP should direct their ire at their corporate IT or infosec team.
it shouldn’t be an option. Some IT departments just see a “more secure” checkbox and will always check it, even if it doesn’t make sense holistically- sometimes compliance incentivises (or forces) this behaviour. A common example is forcing intune/device enrolment for mobile devices (including ipads)- but not for the infinitely less secure laptops: because no such endpoint enforcement checkbox exists
Using a maintained and up-to-date browser is a reasonable requirement for an IT department (should be for anyone really). Would you suggest they should be allowing IE6 just because a user might prefer it?
Of course Google is going to suggest using Chrome, if they detect that the browser might be out of date.
Re: Google workspace threatening to block Firefox access
#26I know Google finally kicked all their employees off alternate browsers but doing it for external customers is definitely a choice
I'm not so sure that enforcing an internal digital monoculture is a productive way to achieve innovation & resilience.
Re: Google workspace threatening to block Firefox access
#27Earlier quoted context omitted.
it shouldn’t be an option. Some IT departments just see a “more secure” checkbox and will always check it, even if it doesn’t make sense holistically- sometimes compliance incentivises (or forces) this behaviour. A common example is forcing intune/device enrolment for mobile devices (including ipads)- but not for the infinitely less secure laptops: because no such endpoint enforcement checkbox exists
Using a maintained and up-to-date browser is a reasonable requirement for an IT department (should be for anyone really). Would you suggest they should be allowing IE6 just because a user might prefer it? Of course Google is going to suggest using Chrome, if they detect that the browser might be out of date.
Is the implication that Firefox is not maintained or?
The issue presented doesn’t seem to be “an up to date browser check” it seems to be a “is it latest chrome” check, which is a very different thing.
Re: Google workspace threatening to block Firefox access
#28I use Google as a secondary search and as of roughly last week it gives me a captcha every time I try to do a search. That had never been the case before.
I am seeing it a lot more lately with uBlock Origin. I've used DDG for search for a while now, but the last few times I've tried Google I got a captcha within a couple of queries if not immediately.
Re: Google workspace threatening to block Firefox access
#29Is it not: https://knowledge.workspace.google.com/admin/security/create... The Org admin can put all sorts of restrictions on who can do what based on the client device setup.
"wow look at all these options available...to limit users to only use software provided by the same corp" you are missing the point entirely.
Re: Google workspace threatening to block Firefox access
#30Does Chromium would still work?