You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Svetoslav Neykov (JIRA)" <ji...@apache.org> on 2017/07/27 13:56:00 UTC

[jira] [Resolved] (JCLOUDS-1321) Per-compute-service credential store

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

Svetoslav Neykov resolved JCLOUDS-1321.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.1.0

https://github.com/jclouds/jclouds/pull/1119 fixes the reported problem

> Per-compute-service credential store
> ------------------------------------
>
>                 Key: JCLOUDS-1321
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1321
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-core
>    Affects Versions: 2.0.2
>            Reporter: Svetoslav Neykov
>             Fix For: 2.1.0
>
>
> With a shared credential store (the current default) the configuration of one compute service leaks in all others, causing the wrong credentials to be used when not overridden.
> The particular problem this fixes - [Azure sets default username/password for images|https://github.com/jclouds/jclouds-labs/blob/master/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/AzureComputeProviderMetadata.java#L98] which leaks to other providers (through [GetLoginForProviderFromPropertiesAndStoreCredentialsOrReturnNull|https://github.com/jclouds/jclouds/blob/master/compute/src/main/java/org/jclouds/compute/config/GetLoginForProviderFromPropertiesAndStoreCredentialsOrReturnNull.java#L51]), causing the wrong username/password to be used.
> Even if the credentials are scoped to a specific provider in the map, it still will cause cross-talk between differently configured compute services. The cache should only apply to the current compute service.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)