[ 
https://issues.apache.org/jira/browse/JCLOUDS-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097315#comment-14097315
 ] 

Werner Buck commented on JCLOUDS-670:
-------------------------------------

Does that not override the username as well ? I.e. the username coming back 
from the image might be good. Will try this now.

> Option force no password when launching images on providers
> -----------------------------------------------------------
>
>                 Key: JCLOUDS-670
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-670
>             Project: jclouds
>          Issue Type: Improvement
>            Reporter: Werner Buck
>            Priority: Minor
>
> Images may return passwords from Nova. I have seen this happen with the 
> official fedora openstack image as well as other times.
> When SSH is used to connect, the password from nova is used, which results in 
> authentication errors while you might want to use the ssh-agent for 
> authentication.
> To fix this I suggest the "forceNoPassword" option, to force the password to 
> be empty even if we receive a password from the provider. This option is by 
> default "false" and can be set in RunScriptOptions or TemplateOptions.
> Github: https://github.com/jclouds/jclouds/pull/486



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to