Google workspace threatening to block Firefox access

This 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.

Is 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.

It appears website developers desperately want to return to a world where browsers actively pretend to be another browser*.

Want to check for DBSC? Enjoy not knowing whether the browser vendor decided to just roll a simple software implementation.

Nothing good comes from browser detection over feature detection anyways. It's time to do away with user-agents and other overt identifying markers, and if we're still not in a better place, aggressively start stubbing features.

* to some degree they still are. Firefox still ships with an user-agent override list for certain websites that have outdated user-agent sniffing for feature detection (and other fixes in about:compat).

It states something about "your organisation's security requirements", do they document what requirements cause this rejection page? Some kind if changed default perhaps?

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.

I know Google finally kicked all their employees off alternate browsers but doing it for external customers is definitely a choice

Not defending it, but given that they use the word "secure" three times in two sentences, I'm wondering if it's shown to browsers that don't support DBSC. Google has been really pushing/overselling this as a magical solution to cookie theft.

Sounds like you have a device policy configured and you should talk to your internal IT/Security team?

Seems like a monopolistic move.

Does Chromium would still work?

I 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.

Oh look, a monopolist is making settings "more secure" by enshrining monopoly more.

And good fucking luck getting the FTC to follow monopoly law.

[flagged]

Smells anticompetitive to me

Do it then