The location of the vault file is an option.
========
ENC_FILE_DIR: the location where the encoded files will be kept. End
with "/" or "\" based on your platform
========
The config for the vault is a one type operation at the jvm level. So I
put it in the security subsystem. I will put it under host and standalone.
========
(05:47:22 PM) bstansberry: asaldhan: yes. i'm suggesting that element
become part of the core config, as a child of <host> or <standalone>. It
should appear in the schema prior to any other element that needs data
from the vault.
=============
On 08/31/2011 03:30 PM, Brian Stansberry wrote:
No opposition.
Where do you see the vault being located on the filesystem?
Also, right now the vault config is in the security subsystem, but to
make it usable by the core AS I think we'll need to pull it out and make
it an element under<standalone>,<host> etc.
On 8/31/11 2:10 PM, Anil Saldhana wrote:
> Hi All,
> I am currently working on providing a means to secure attributes such
> as passwords. I have come up with the notion of a vault that stores the
> attributes
>
> JIRA:
https://issues.jboss.org/browse/AS7-1622
> Discussion:
http://community.jboss.org/thread/170598?tstart=0
>
> I need to create two scripts (vault.sh and vault.bat) in the bin
> directory of the AS.
>
> Is there any opposition to creating the scripts?
>
> Regards,
> Anil