|
From: Daniel F. <dfe...@us...> - 2008-11-19 01:21:25
|
Hello, If you restarted your sever, there is no way hibernate or jasypt stick to previously set values... as they should have been lost when the JVM process died. From your explanation, I would certainly double-check the encryption configuration just to be sure that the same old values (algorithm etc) are in fact not being set again... Regards, Daniel. jbolger wrote: > +------------------------+ > Jasypt Users List > http://www.jasypt.org > +------------------------+ > > Hi, > > Our client have a requirement that the encryption values (password/key > iteration values) could be updated from time to time. > > Therefore, what we are thinking is that you would pull out all of the > existing data with the old encryption values, update the encryptors to use > the new values and then re-encrpyt the data. > > This appeared to work at first as I could still view the data after updating > encryption. However, when I restarted the server, I got an > EncryptionOperationNotPossibleException exception. > > So it looks to me like, Hibernate or Jasypt holds onto the original > encryptors even if I am calling the register method on them again. > > My question is, is there a way of unregistering encryptors and force > Hibernate/Jasypt to use a new and updated Encryptor? Or is there a better > way of meeting this requirement? > > Thanks very much, > John > |