For an application that I've already in production and where I cannot change passwords, is there a backwards-compatible configuration?
Also, I had transaction problems when logging in and I had to apply the txAdvice also to the userDao bean to make everything work, is this problem only mine, or the userDao passed to Spring Security should be a userManager instead with the proper surrounding transaction handling? Thanks, Marcello -- http://magomarcelo.blogspot.com http://www.jugmilano.it mraible wrote: > > What does your security.xml look like? In the SVN right now, we have a > salt for password encryption. In the 2.0.1 version of AppFuse we did > not. To make tests pass in 2.0.2, you'll need to update passwords in > sample-data.xml. > > Matt > > On Thu, Apr 17, 2008 at 1:54 PM, <[EMAIL PROTECTED]> wrote: >> I'm following guide on Matt Raible's site on upgrading acegi to spring >> security. >> >> After few hours, finally I can run my application. But new problem >> arise, now I can not >> log in into application with no visible error on log. I guess I missed >> minor detail while >> upgrading. >> >> Matt, could you give me some advice; anything that I should check to >> make it work ? >> >> Many thanks! >> >> -- >> Ernas M. Jamil >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Upgrading-to-Spring-Security-tp16754559s2369p16762948.html Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
