Bug 1039169 - Hardcoded default vault paths in configuration files
Summary: Hardcoded default vault paths in configuration files
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Installer
Version: 6.0.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER8
: 6.0.0
Assignee: Thomas Hauser
QA Contact: Len DiMaggio
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-06 19:55 UTC by kconner
Modified: 2014-02-06 15:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

Description kconner 2013-12-06 19:55:22 UTC
An example of this is the standalone.xml file that contains a hardcoded path for KEYSTORE_URL and ENC_FILE_DIR.

Could we have these default to

        <vault-option name="KEYSTORE_URL" value="${jboss.server.config.dir}/vault.keystore"/>
        <vault-option name="ENC_FILE_DIR" value="${jboss.home.dir}/vault/"/>

Comment 1 Thomas Hauser 2013-12-13 16:41:18 UTC
Finally fixed in e85daeb8623a25e90e06c98fae6d85d03a2daf76
 of installer-commons and 9f192f11fd9121db64f08e3a6b175f48ad33a402 of fsw-installer and 5ba0ac0213c1bbace3ea49b50e030fc0f7929909 of sramp-installer.

Note that when a user chooses a custom vault installation rather than using the default, the vault paths cannot contain properties.

Comment 2 Len DiMaggio 2014-01-08 15:44:55 UTC
Verified in ER8:

grep KEYSTORE_URL standalone.xml 
<vault-option name="KEYSTORE_URL" alue="${jboss.server.config.dir}/vault.keystore"/>

grep ENC_FILE_DIR standalone.xml 
<vault-option name="ENC_FILE_DIR" value="${jboss.home.dir}/vault"/>


Note You need to log in before you can comment on or make changes to this bug.