| Summary: | Hardcoded default vault paths in configuration files | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | kconner |
| Component: | Installer | Assignee: | Thomas Hauser <thauser> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Len DiMaggio <ldimaggi> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0 GA | CC: | ncross, soa-p-jira |
| Target Milestone: | ER8 | ||
| Target Release: | 6.0.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
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. 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"/>
|
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/"/>