If you can't login, it's likely related to security.xml or sample-data.xml. Did you change sample-data.xml at all for 2.0.2? What are your usernames and passwords in that file? If you can post them, I can compare and tell you what the plain-text passwords are. If your security.xml matches the one in SVN, then it's possible that you don't have a passwordEncoder bean properly defined in applicationContext-service.xml. You could change your sample-data.xml to use plain text passwords to see if password encryption is turned on.
Matt On Fri, May 16, 2008 at 3:46 AM, Martin Homik <[EMAIL PROTECTED]> wrote: > > I still cannot login with "user" nor with "admin". However, both are in the > database. When I try to create a new "user", I get the message that the user > is in the database. When I request for sending the user's password, I get > the message that the user is not in the database. > > I fear, there are some more differences between AppFuse 2.0.1 and AppFuse > 2.0.2 not mentioned in the release notes. For instance, I came across > different result types ins struts.xml. It used to be type="redirect", now it > is type="action-redirect". I don't know whether they have any affect, but > they could. > > If I don't manage to fix the login problem, I'll give up the update and go > on with 2.0.1. > > Cheers! > > > > > Martin Homik wrote: >> >> I managed somehow to run my project, Things that I made differently: >> * as I run war:inplace I had a few files that needed an update. >> --> checked out a fresh project and made a war:inplace to get all the >> up to date files >> * replaced my security.xml by the new one >> * in footer.jsp: replaced <authz:authentication property="fullName"/> by >> <security:authentication property="principal.fullName"/>. >> * don't add dependencies as stated at: >> http://raibledesigns.com/rd/entry/upgrading_to_spring_security_2 >> * in logout.jsp: replace >> TokenBasedRememberMeServices.ACEGI_SECURITY_REMEMBER_ME_HASHED_COOKIE_KEY >> by TokenBasedRememberMeServices.SPRING_SECURITY_REMEMBER_ME_COOKIE_KEY >> * I experimented with contextApplication-service.xml, so I deleted it from >> my src folder such that it does not override the standard configuration >> file. >> * in addition to replace all org.acegisecurity, also search for any >> occurences of "acegi*" and replace carefully. >> >> So far so good, jetty is up and running, but there is still one problem: I >> can't login. Not with 'admin', nor with 'user'. I get a nice error >> message, but no exception is thrown in the console. Don't know whether it >> is verified and against what. >> >> Any idea, where to look? >> >> >> >> >> >> > > -- > View this message in context: > http://www.nabble.com/AppFuse-2.0.2--Jetty-6.1.9-still-accesses-org-acegisecurity-tp17232823s2369p17271090.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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
