[jira] [Commented] (KARAF-4880) Can't use Client from a script when passwords are encrypted

["Paul McCulloch (JIRA)" <ji...@apache.org>]

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

Paul McCulloch commented on KARAF-4880:
---------------------------------------

"With clear text passwords client reads the passwords from users.properties."
Not quite true  - with clear passwords & no -u option specified an arbitrary user is chosen from the properties file & logged in. The user chosen is determined by the iteration order of a HashSet (which is undefined).

> Can't use Client from a script when passwords are encrypted
> -----------------------------------------------------------
>
>                 Key: KARAF-4880
>                 URL: https://issues.apache.org/jira/browse/KARAF-4880
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 4.0.7
>            Reporter: Paul McCulloch
>            Assignee: Jean-Baptiste Onofré
>
> Without the old -p option there is no straightforward way to use the client to connect to a karaf using encrypted password authentication.
> With clear text passwords client reads the passwords from users.properties.
> My use case is an (izpack) installer which uses the client to add features & apply configurations. The installer prompts the user for admin account details & should pass these to the client. 
> Using SSH keys is problematic I believe. I would need the user (or the installer) to keep a copy of the key generated on initial installation for use in subsequent upgrades.
> My installer is cross platform, so relying on open SSH etc. as a workaround is problematic.
> The -p option was removed from client as part of KARAF-1475 (https://github.com/apache/karaf/commit/d6838dd5a12a13b99c534981273abdbbee5b7f22)



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