Since a while I observe the following "problem" when I am using chromium as webbrowser. Every time chromium is closed, and quit, it loses the authentication for services such as Gmail and Hangouts. It forces a login, but does remember it has been signed on before and does not pop up 2FA. Specifically Hangouts has the behavior that it will show "as if you are signed in" but sends a "400", after which an reload of the pages forces sign in. I wonder if this is related to the removal of API keys in chromium, but the behavior obviously breaks their own services. I see this behavior with 91.x and now 92.x. I have removed the full chromium config directory, so I am quite sure it is not about a stale cookie. Reproducible: Always
Can confirm this happening.
Stefan - did you ever find a workaround to this?
(In reply to Jason A. Donenfeld from comment #2) > Stefan - did you ever find a workaround to this? Nope... and I wonder if I should be surprised surprised upstream does not care about their own SSO authentication.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fce48ef271bbcaee9afdf0481294da167e665a9b commit fce48ef271bbcaee9afdf0481294da167e665a9b Author: Jason A. Donenfeld <zx2c4@gentoo.org> AuthorDate: 2021-08-07 21:53:29 +0000 Commit: Jason A. Donenfeld <zx2c4@gentoo.org> CommitDate: 2021-08-08 11:50:05 +0000 www-client/chromium: work around dead oauth2 credentials Google doesn't let us bake in OAuth2 credentials, and for some time, Google sign-in has been broken. Arch dealt with this in March, and so did we to some degree, but in the last few months, our sign-in credentials have been broken. It appears that we actually did remove API credentials in March around Chrome 89, but they got added back, perhaps when rotating newer versions to replace older versions. Work around this by following Arch's lead: we remove the predefined credentials, as before, but also we patch Chromium so that people can use their own easily, using Arch's patch for that. For more info, see: https://archlinux.org/news/chromium-losing-sync-support-in-early-march/ https://bodhi.fedoraproject.org/updates/FEDORA-2021-48866282e5 https://hackaday.com/2021/01/26/whats-the-deal-with-chromium-on-linux-google-at-odds-with-package-maintainers/ Closes: https://bugs.gentoo.org/791871 Package-Manager: Portage-3.0.20, Repoman-3.0.3 Signed-off-by: Jason A. Donenfeld <zx2c4@gentoo.org> www-client/chromium/chromium-92.0.4515.107.ebuild | 12 +++++++----- www-client/chromium/chromium-92.0.4515.131.ebuild | 12 +++++++----- www-client/chromium/chromium-93.0.4577.25.ebuild | 12 +++++++----- www-client/chromium/chromium-94.0.4595.0.ebuild | 12 +++++++----- ...chromium-use-oauth2-client-switches-as-default.patch | 17 +++++++++++++++++ 5 files changed, 45 insertions(+), 20 deletions(-)
Stefan - given that a version bump is coming so soon, we didn't revbump the packages. But if you'd like to try this out now, just rebuild chromium.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=0a960c2aadd2b98513ada135c437d8a6701e1f84 commit 0a960c2aadd2b98513ada135c437d8a6701e1f84 Author: Jason A. Donenfeld <zx2c4@gentoo.org> AuthorDate: 2021-08-11 00:54:59 +0000 Commit: Jason A. Donenfeld <zx2c4@gentoo.org> CommitDate: 2021-08-11 00:56:46 +0000 2021-08-11-oauth2-creds-chromium: OAuth2 Credentials Removed from Chromium Bug: https://bugs.gentoo.org/791871 Signed-off-by: Jason A. Donenfeld <zx2c4@gentoo.org> .../2021-08-11-oauth2-creds-chromium.en.txt | 44 ++++++++++++++++++++++ 1 file changed, 44 insertions(+)
