Workaround for Bug MRM-728

["von Janowsky, Simon" <vo...@consist.de>]

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.

Re: Workaround for Bug MRM-728

[Brett Porter <br...@gmail.com>]

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 <vo...@consist.de>

>  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/