You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by "Sumukh Sridhara (JIRA)" <ji...@apache.org> on 2016/12/31 10:01:10 UTC

[jira] [Closed] (LIBCLOUD-885) Google Authentication does not detect IAM service accounts

     [ https://issues.apache.org/jira/browse/LIBCLOUD-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sumukh Sridhara closed LIBCLOUD-885.
------------------------------------
    Resolution: Duplicate

Apologies. It appears to have been resolved in the latest version of libcloud.

> Google Authentication does not detect IAM service accounts
> ----------------------------------------------------------
>
>                 Key: LIBCLOUD-885
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-885
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Storage
>            Reporter: Sumukh Sridhara
>            Priority: Minor
>              Labels: google, google-cloud-storage
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> The current code to guess what authentication mode is being used assumes that all services accounts end in 'developer.gserviceaccount.com' but that is no longer true for service accounts that use IAM. Those accounts end with '@<project-name>.iam.gserviceaccount.com' 
> https://cloud.google.com/iam/docs/service-accounts#product_name_short_service_accounts
> The current authentication will not work for these service accounts and the library will fallback to an installed application auth flow (which prompts for user input to do out of band OAuth) 
> Relevant Commit: 3849f65fe5289f7d7160b7537afa930c7e2ea8a8



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)