[Pkg-chromium-maint] Bug#766850: Bug#766850: chromium: Login to Chromium using custom API keys leads to error "Service unavailable. Try again later."

[Vincent Bernat]

 ❦ 26 octobre 2014 11:27 +0100, Jean Baptiste Favre <debian at jbfavre.org> :

> Since upgrade to version 38, API keys are not included anymore.
> To be able to use the Google Sync feature, I followed instructions given here:
> www.chromium.org/developers/how-tos/api-keys
>
> I registered and get API credential which were added as ENV variables in
> /etc/chromium.d/googleapikeys as follow:
>
> export GOOGLE_API_KEY="api_key"
> export GOOGLE_DEFAULT_CLIENT_ID="my_client_id.apps.googleusercontent.com"
> export GOOGLE_DEFAULT_CLIENT_SECRET="client_secret"
>
> Starting chromium with this file prevents the "API keys are missing" top bar
> notification.
>
> Trying to login with the Gmail account used to create custom API keys works,
> but leads to "Service unvailable. Try again later." message.
>
> I've double-checked my API credential without success.

You can use the Debian API keys instead. I put this in mine and it
works:

export GOOGLE_API_KEY="AIzaSyCkfPOPZXDKNn8hhgu3JrA62wIgC93d44k"
export GOOGLE_DEFAULT_CLIENT_ID="811574891467.apps.googleusercontent.com"
export GOOGLE_DEFAULT_CLIENT_SECRET="kdloedMFGdGla2P1zacGjAQh"

Maybe try with them instead.
-- 
Make sure every module hides something.
            - The Elements of Programming Style (Kernighan & Plauger)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-chromium-maint/attachments/20141026/98b60504/attachment.sig>