So security.properties is now in 3 places on our server: - /usr/local/apache-archiva-1.1/conf - /var/lib/archiva/conf - ~/.m2
I restarted archiva and I still see the same behavior: I can sign in with the admin user, but when I try to sign in as another user, it doesn't sign in, no error messages, just takes me to the Search screen. If I then sign in as admin again, that other user is locked under User Management. Even if I change that user's password as the admin, I still can't sign in with that other user. Any ideas on how to make Archiva just be happy with this other user, and not keep locking them out? Wendy Smoak-3 wrote: > > On Mon, Feb 9, 2009 at 8:10 AM, Zach Cox <[email protected]> wrote: >> >> Thanks KUno, that looks promising. I'm running the Archiva 1.1 >> standalone, >> not through Tomcat. Do you know where I should put that >> security.properties >> file? > > In the standalone install, you can put it in the 'conf' directory. > > http://archiva.apache.org/docs/1.2-M1/adminguide/customising-security.html > > -- > Wendy > > -- View this message in context: http://www.nabble.com/Archiva-will-not-stop-forcing-password-resets%21-tp21792131p21935069.html Sent from the archiva-users mailing list archive at Nabble.com.
