[
https://issues.apache.org/jira/browse/JCLOUDS-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097900#comment-14097900
]
Werner Buck edited comment on JCLOUDS-670 at 8/14/14 11:28 PM:
---------------------------------------------------------------
Yeah I explicitly put it in the portable option. I added it to Nova because
they appear to be overriding the override credentials methods for some reason.
I agree that this opens up more shortcuts like this. I can't test
overrideLoginCredentials function yet, though the naming does not make clear
that it can be used as a "final" forced override.
The use case is: override passwords/usernames/privatekeys with empty if we want
to. The current overrideX functions should imply that whenever I use it, its
content will be used including when that content is empty.
What about this, we turn overrideXX functions into Optional<String>. The catch
is, that they can be nullable and is default null. When set to null Jclouds
will ignore the override, when however it IS not null it will always override
the password with the Optional content. If the Optional isPresent, then its
content will be used. If the Optional is notpresent (but also not null) it will
force the password/privatekey/username to be null as well.
was (Author: wernerbu):
Yeah I explicitly put it in the portable option. I added it to Nova because
they appear to be overriding the override credentials methods for some reason.
I agree that this opens up more shortcuts like this. I can't test
overrideLoginCredentials function yet, though the naming does not make clear
that it can be used as a "final" forced override.
The use case is: override passwords/usernames/privatekeys with empty if we want
to. The current overrideX functions should imply that whenever I use it, its
way is law. And you should be able to set it to empty.
What about this, we turn overrideXX functions into Optional<String>. The catch
is, that they can be nullable and is default null. When set to null Jclouds
will ignore the override, when however it IS not null it will always override
the password with the Optional content. If the Optional isPresent, then its
content will be used. If the Optional is notpresent (but also not null) it will
force the password/privatekey/username to be null as well.
> 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)
