In the next RC this problem will be fixed, and you'll get the = back in the string.
If you need it earlier, you can check out wicket trunk and build your own wicket version.
Martijn
On 4/18/06,
Rüdiger Schulz <[EMAIL PROTECTED]> wrote:
Hello list,
for a Wicket-application requiring a signed-in user I use
PasswordTextField.getModelObject() for acquiring the entered data.
Going the easy way, I simply stored this in the database, as it was
already encrypted, and comparison during login is also very easy to
do.
Now I upgraded from wicket 1.1.1 to 1.2rc1. This method still works,
but something has changed. Before, all passwords had a '=' as their
last character, which they now lack. Apart from that, the encryption
seems to produce the same encrypted strings out of the source strings.
If this is not a bug, it should be stated in the migration guide
somewhere...
--
greetings from Berlin,
Rüdiger Schulz
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
--
Wicket 1.2 is coming! Write Ajax applications without touching _javascript_!
-- http://wicketframework.org
