Daniel Fernández Garrido wrote: > David, I think your problem (not wanting password to come encrypted from the > input component) would be solved by simply making your Application object > return your own implementation of the > wicket.settings.ISecuritySettingsinterface for its getSecuritySettings > method. And in this extension > (MySecuritySettings, for instance) make that the getCryptFactory method > return a wicket.util.crypt.NoCryptFactory object. > > This way you would be able to use PasswordTextField component while not > getting your text encrypted from it. > > Regards, > Daniel.
Hmmm ... well, I guess I'll do that if I have to. But (despite my initial message) I think I actually don't have a problem with Wicket encrypting the password internally (as long as it gets delivered to the model and the model target unencrypted). But as per the bug I found, it looks like perhaps I ran into a case where Wicket is encrypting the password field when it shouldn't be. As long as it was working correctly, though, (or there's some workaround) then I guess I don't really have any need to bypass the internal encryption. Thanks, DR ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
