- A vault property has been specified in the JBoss configuration (either in XML configuration or through CLI), but is not present in the vault in-memory values. This may be because the value has not been stored with bin/vault.sh or that EAP wasn't restarted since the value was added. Vault is only parsed at startup, so if you store a value in vault with EAP running it won't be picked up until next restart.
- Use bin/vault.sh to store the value you want to be masked in the configuration. Then reload through the CLI or restart EAP to pickup the stored value.
In my case the value wasn't actually in the vault due to a scripting error.
The error handling here leaves much to be desired. Instead of "Null input buffer",
the Exception should say "value not found for the supplied key" or something aliong those lines.
Null input buffer makes it seems like a configuration or initialization problem with the vault.
The message about "attempt to create a second Security vault..." i understand now this is a known issue and an erroneous message that can be ignored.