A solution would be to extend an existing configuration and override
getProperty and addPropertyDirect to decode/encode the value on the fly
if the key contains 'password'.
Emmanuel Bourg
[EMAIL PROTECTED] a écrit :
Thanks. Just to confirm: there is no facility by which I could specify
my Base64 encoder as a closure (a transformer) to Configuration, so
it my plugins are executed in sequence before setValue() as follows?
{invoke plugin 1} => {invoke plugin 2} ... => Finally Invoke setValue()
Thanks,
/U
-------------- Original message ----------------------
From: Oliver Heger <[EMAIL PROTECTED]>
[EMAIL PROTECTED] wrote:
Is there a way to have Commons PropertyConfiguration encrypt the specified
value
with a given scheme before it persists them? This is particularly useful for
persisting passwords (although you could argue that passwords should not be
persisted in peroperty files).
Do I need to extend commons configuration?
Thanks,
/U
Configuration does not provide a means for encrypting properties. I fear
you have to do the encryption yourself and store the encrypted password
(e.g. as a Base64-encoded string) as a property.
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
