[
https://issues.apache.org/jira/browse/LIBCLOUD-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291969#comment-14291969
]
ASF subversion and git services commented on LIBCLOUD-657:
----------------------------------------------------------
Commit ab7d07bd4e7197c275a926de8d9639de9bc234a6 in libcloud's branch
refs/heads/trunk from [~erjohnso]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=ab7d07b ]
[google compute] Add support for JSON private key format
Closes #438
Closes LIBCLOUD-627
Closes LIBCLOUD-657
Signed-off-by: Eric Johnson <[email protected]>
> Update Google auth to support new JSON key format
> -------------------------------------------------
>
> Key: LIBCLOUD-657
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-657
> Project: Libcloud
> Issue Type: New Feature
> Components: Compute
> Reporter: Eric Johnson
> Assignee: Eric Johnson
>
> Google introduced a new Service Account key format (JSON) and over time this
> will likely become the preferred format. We should begin by supporting this
> new format soon. If Google does make this the default, we may want to
> follow-up and issue a (debug | info) warning to users relying on P12 format.
> AFAIK, there is no clear documentation on this format. However, if you open
> up the Developers Console and look under "APIs & Auth" -> "Credentials",
> you'll see the "Generate New JSON Key" button next to any existing Service
> Accounts (or be given the option to create one with a new SA).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
