I was wrong. Seems that the security properties just extended the time between the lock-outs. It doesn't even make a difference if I declare the Hudson User as a Administrator....
Now my questions: What are the reasons that a user can get locked? Can I manipulate this in any way, perhaps by setting a flag in the database? I really need help here :-( Greetings, Simon. -----Ursprüngliche Nachricht----- Von: Brett Porter [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 5. September 2008 11:39 An: [email protected] Betreff: Re: Workaround for Bug MRM-728 sory, should have read this before responding to the older post :) The login attempts should be the number of failed attempts, so if hudson has the right credentials it shouldn't matter what the setting is. Probably it was the password that was expired? - Brett 2008/9/5 von Janowsky, Simon <[EMAIL PROTECTED]> > Hello, > since my Archiva always kept locking my user for the CI-System > (Hudson) I changed some settings in the security.properties files as > described in the documentation. > > <security.properties> > # Security Policies > security.policy.password.expiration.enabled=false > security.policy.password.expiration.days=0 > security.policy.allowed.login.attempt=50 > security.policy.strict.enforcement.enabled=false > </security.properties> > > Now for three days it seems to work (No Lock-outs). My wild guess ist > that Hudson logged in to often into the system, (login.attempts were > too low) and locked the User? > > Muchos saludos, > Simon. > -- Brett Porter Blog: http://blogs.exist.com/bporter/
smime.p7s
Description: S/MIME cryptographic signature
