| 1 |
Title: OAuth2 Credentials Removed from Chromium |
| 2 |
Author: Jason A. Donenfeld |
| 3 |
Posted: 2021-08-08 |
| 4 |
Revision: 1 |
| 5 |
News-Item-Format: 2.0 |
| 6 |
Display-If-Installed: www-client/chromium |
| 7 |
|
| 8 |
In March of this year, Google announced that OAuth2 credentials would be revoked |
| 9 |
for distros shipping Chromium. This was covered in multiple places at the time, |
| 10 |
such as [1,2,3]. Around that time, with 89.0.4389.82, Gentoo removed OAuth2 |
| 11 |
credentials from its packages. However, they slipped back in shortly after. As |
| 12 |
a result, some users [4] have found that recently Google's SSO does not persist |
| 13 |
between browser sessions; e.g. you have to log back into GMail every time you |
| 14 |
open your browser. Today's changes [5] restore the old behavior we had in March, |
| 15 |
of not shipping Gentoo OAuth2 credentials. It also imports a patch from |
| 16 |
Archlinux that enables users to pass the --oauth2-client-id= and |
| 17 |
--oauth2-client-secret= command-line switches to supply such credentials. If you |
| 18 |
find that certain Google services are no longer working, you may wish to set |
| 19 |
these flags, obtaining credentials by following the instructions at [6]. |
| 20 |
However, even without supplying such credentials, Google's SSO now should be |
| 21 |
working as expected. |
| 22 |
|
| 23 |
[1] https://archlinux.org/news/chromium-losing-sync-support-in-early-march/ |
| 24 |
[2] https://bodhi.fedoraproject.org/updates/FEDORA-2021-48866282e5 |
| 25 |
[3] https://hackaday.com/2021/01/26/whats-the-deal-with-chromium-on-linux-google-at-odds-with-package-maintainers/ |
| 26 |
[4] https://bugs.gentoo.org/791871 |
| 27 |
[5] https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fce48ef271bbcaee9afdf0481294da167e665a9b |
| 28 |
[6] http://www.chromium.org/developers/how-tos/api-keys |
Archives