Issue

• Why does a vault encrypted datasource password fail to work when used in a *-ds.xml file in JBoss EAP 6?
• The same vault encrypted password works when the datasource is defined in the standalone.xml file.
• in old JBoss EAP version like 5.1 or 5.2, it was possible to deploy datasources and security domains in separate files, like -ds.xml. But in JBoss EAP 6.x it is now impossilbe, because everything must/should be configured in standalone.xml.
• We have many applications which have their dependent datasources and different combinations of these applications will be deployed in different JBoss instances. In addition with different environments. With the single standalone.xml it is very difficult to maintain our requirement, because you must edit the standalone.xml for each JBoss instance or you must use CLI to setup this configuration, for every new instance and for every migration.
• Is it possible to bundle datasource and its security domain in a separate deployment file? if yes, could you please provide us an example?