Problems with instructions on using own API key

[scaramouche1]

The instructions on "Using your own API key" seem to be outdated or incomplete. Google's Cloud Console doesn't seem to offer a way to download a client_secret.json file. Instead, it directly offers an API key, but it's unclear how to pass this to lieer.

[bcspragu]

The term "API key" is likely what's confusing people here:

You want the "OAuth client ID" option here, not the "API key" option

With that, it works fine for me. Creating an OAuth2 client gives you a client_id and a client_secret, and the download button looks like this for me:

[gauteh]

Good point. Would be great to update the instructions with this screenshot 😁

[bcspragu]

For sure, feel free to use them! (I can also send the PR if you'd prefer)

[gauteh]

For sure, feel free to use them! (I can also send the PR if you'd prefer)

That would be awesome!

[bcspragu]

Sounds good, writing those up now! One question for you: for the public OAuth2 credentials, the only "Redirect URI" set is localhost:xxxx, right? Just adding a brief section on the extremely minor risks of using the public creds

[gauteh]

I plan to remove the public credentials, see linked issue above.