-
Bug
-
Resolution: Won't Do
-
Minor
-
None
-
3.0.0.Beta27
-
None
Executing this command:
/host=master/core-service=vault:add(vault-options={"KEYSTORE_URL" => "C:\wildfly_slave\wildfly-11.0.0.Alpha1\domain\configuration\keystore.vault", "KEYSTORE_PASSWORD" => "Password01", "KEYSTORE_ALIAS" => "vault", "SALT" => "12345678", "ITERATION_COUNT" => "50", "ENC_FILE_DIR" => "C:\wildfly_slave\wildfly-11.0.0.Alpha1\domain\configuration\vault"})
Will result in this element in the XML:
</extensions> <vault> <vault-option name="KEYSTORE_URL" value="C:\wildfly_slave\wildfly-11.0.0.Alpha1\domain\configuration\keystore.vault"/> <vault-option name="KEYSTORE_PASSWORD" value="MASK-223/wEo1GLELe8EuQa5u20"/> <vault-option name="KEYSTORE_ALIAS" value="vault"/> <vault-option name="SALT" value="12345678"/> <vault-option name="ITERATION_COUNT" value="50"/> <vault-option name="ENC_FILE_DIR" value="C:\wildfly_slave\wildfly-11.0.0.Alpha1\domain\configuration\vault/"/> </vault>
Note the incorrect slash on the end of the ENC_FILE_DIR option. I assume this value is being normalised to include a trailing slash, but the wrong character is being selected on a Windows system.
WildFly seems quite happy with this incorrect character, but external tools reading this path have to account for the unexpected value.