seems archiva 2.2 ignoring security properties
i following document: have set security.properties file under
d:\apache\archiva-2.2.0\conf
when setting new password user in archiva ui still getting:
must provide password containing @ least 1 numeric character(s).
security.properties content:
# security policies #security.policy.password.encoder= security.policy.password.previous.count=9999 security.policy.password.expiration.days=99999 security.policy.password.expiration.enabled=false security.policy.allowed.login.attempt=3 # password rules security.policy.password.rule.alphanumeric.enabled=false security.policy.password.rule.alphacount.enabled=false security.policy.password.rule.alphacount.minimum=0 security.policy.password.rule.characterlength.enabled=true security.policy.password.rule.characterlength.minimum=3 security.policy.password.rule.characterlength.maximum=0 security.policy.password.rule.musthave.enabled=false security.policy.password.rule.numericalcount.enabled=false security.policy.password.rule.numericalcount.minimum=0 security.policy.password.rule.reuse.enabled=false security.policy.password.rule.nowhitespace.enabled=true
stop running , make backup of conf/archiva.xml file.
example:
service archiva stop cp archiva.xml archiva.xml.orig
edit config values want modify within main xml configuration file: conf/archiva.xml
changing numeric character count:
<numericalcount> <minimum>0</minimum> <enabled>false</enabled> </numericalcount>
changing password expiration limit:
<expiration> <enabled>false</enabled> <days>999999</days> </expiration>
these values should in config file (they in mine). perhaps copied there after unsuccessful attempts configure them through web ui.
additionally, prevent user caching behaviour while you're making changes:
<useuserscache>false</useuserscache>
start again:
service archiva start
Comments
Post a Comment