[
https://issues.jboss.org/browse/WFLY-2636?page=com.atlassian.jira.plugin....
]
Alexey Loubyansky resolved WFLY-2636.
-------------------------------------
Resolution: Done
'ssl' element in jboss-cli.xml now has an optional child (first child in the
sequence) element 'vault', which has a required attribute 'file', the
value of which could be either an absolute or a relative path to the vault XML
configuration file (the content of which is generated using vault.[sh|bat]).
'vault' element also has an optional attribute 'relative-to', which if
present will indicate that the value of the required attribute 'file' should be
used as a relative to the value of 'relative-to' path. The value of
'relative-to' can be one of the named system-provided paths such as:
jboss.home.dir, user.home or user.dir.
The following elements in the ssl configuration support vault-encrypted values:
- key-store-password;
- key-password;
- trust-store-password.
cli should be able to use the vault to encrypt a keystore password
------------------------------------------------------------------
Key: WFLY-2636
URL:
https://issues.jboss.org/browse/WFLY-2636
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: CLI
Reporter: Kabir Khan
Assignee: Alexey Loubyansky
Fix For: 8.0.0.Final
The CLI can be configured for two-way SSL to connect to the management interface. The
password for keystore/truststore is currently limited to being plain text inside the
"jboss-cli.xml" file.
This request is to allow a CLI client to use a local vault to encrypt those password
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira