| 1 |
Hi, |
| 2 |
|
| 3 |
updated based on previous suggestions. |
| 4 |
|
| 5 |
``` |
| 6 |
Title: Chromium access to Google services |
| 7 |
Author: Stephan Hartmann <sultan@g.o> |
| 8 |
Content-Type: text/plain |
| 9 |
Posted: 2021-03-09 |
| 10 |
Revision: 1 |
| 11 |
News-Item-Format: 2.0 |
| 12 |
Display-If-Installed: www-client/chromium |
| 13 |
|
| 14 |
Starting March 15th, 2021 Google Chrome Team will restrict access to |
| 15 |
Google APIs and services that are reserved for Google use only. This |
| 16 |
means that users are no longer able to login into their Google Accounts |
| 17 |
which disables access to for example Chrome Sync. |
| 18 |
|
| 19 |
As a consequence we have to remove Client ID and secret from all |
| 20 |
www-client/chromium ebuilds. This change has already been done for |
| 21 |
=www-client/chromium-89.0.4389.82. Other versions will be updated |
| 22 |
shortly. |
| 23 |
|
| 24 |
If you need one of the Google use only APIs, then you either have to |
| 25 |
switch to www-client/google-chrome{-beta,-unstable} or setup your own |
| 26 |
keys [1]. However, the latter is only intended for development. |
| 27 |
Documentation on how to generate and use own keys can be found in [2]. |
| 28 |
|
| 29 |
[1] |
| 30 |
https://groups.google.com/a/chromium.org/g/chromium-dev/c/jgy5pcJ7np8/m/p3j_4b6vBQAJ |
| 31 |
[2] https://www.chromium.org/developers/how-tos/api-keys |
| 32 |
``` |
| 33 |
|
| 34 |
Best regards, |
| 35 |
|
| 36 |
Stephan |
Archives