[JIRA] [google-oauth] (JENKINS-24571) support private keys from new google developer console

Wed, 03 Sep 2014 19:52:10 -0700

Issue Type: Improvement Improvement
Affects Versions: current
Assignee: Unassigned
Components: google-oauth
Created: 03/Sep/14 8:41 PM
Description:

The new Google Developer Console provides two kind of private keys.

the first one is a json file which contains all the information that is necessary to authenticate with a service account. this file gets downloaded when you create a new service account in the Google Developer Console.

it's structure is as follows:

{
  "private_key_id": "...",
  "private_key": "-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----\n",
  "client_email": "...@developer.gserviceaccount.com",
  "client_id": "...apps.googleusercontent.com",
  "type": "service_account"
}


the second type of private key is a .p12 file. it can be also downloaded in the Google Developer Console. this file is a PKCS12 keystore and contains a private key that can be used to authenticate a service account. the keystore password and key password is "notasecret". the key alias is "privatekey".



it would be nice to let the user choose between this two options when creating google oauth credentials in jenkins.
Project: Jenkins
Labels: plugin
Priority: Major Major
Reporter: David Hamm
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to