Directions for GCE service account no longer work. about google-oauth-plugin HOT 5 CLOSED

Seems like you just need a JSON file with {"web":{"client_email": ""}}, maybe better just to have a text field for the client email from the service account.

from google-oauth-plugin.

Yeah, this seems to have changed — only "Create new Client ID" followed by choosing "Web application" (rather than "Service account") leads to the "Download JSON" button mentioned in the plugin. Creating a Service account and hitting "Generate new JSON key" generates a new key pair and outputs a different JSON format.

Being able to just enter the client email ID would be easiest. Failing that, maybe requiring only the service account JSON file, as it seems to contain all the details required, including private key?
(I'm trying to use this plugin for the Android publisher API, which seems to need a service account rather than an web app OAuth client)

Any thoughts, @mattmoor?

from google-oauth-plugin.

It seems the correct JSON file can still be downloaded from the old console at https://code.google.com/apis/console?noredirect — there you can hit the "Download JSON" link.

That JSON file works fine with this plugin, and I was able to access the Android scope with my service account.

Note the noredirect to avoid being redirected to the nice new console.developers.google.com version, which doesn't have the JSON option :)

from google-oauth-plugin.

wouldn't it be nice to give the user the options how he provides the service account email address and private key?

first option would be to provide this data through the json file downloaded from the new cloud console. it seems to contain everything that is needed.

secend option would be to just let the user input the email address and private key in textboxes.

i personally would prefer the second option but to make it easy for the user also let him provide the json file.

from google-oauth-plugin.

Updating documentation tracked by #71

from google-oauth-plugin.