[
https://issues.apache.org/jira/browse/MRM-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Stockhammer resolved MRM-1913.
-------------------------------------
Resolution: Cannot Reproduce
I don't see why it should not be possible to set the expiration days to more
than 90 days.
Please check with an current archiva version.
If this is still an issue you can reopen it.
> Can't change expiry configuration of archiva user
> -------------------------------------------------
>
> Key: MRM-1913
> URL: https://issues.apache.org/jira/browse/MRM-1913
> Project: Archiva
> Issue Type: Bug
> Components: Users/Security
> Affects Versions: 2.2.0
> Environment: Linux
> Reporter: John Schmidt
> Priority: Major
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Users for Apache Archiva can't have passwords that never expire. In fact, in
> my tests, if I change security.policy.password.expiration.days to anything
> greater than 90, it ignores it. Thus, every 90 days our developers are
> locked out of apache archiva until I remove and recreate the user database.
> Emails warning us of this expiration never get out, even though the users in
> question have a valid email address attached.
> Please give us either one of two fixes:
> -Allow security.policy.password.expiration.days to be more than 90 days
> -Allow the ability to disable password expiry
> Resources:
> https://archiva.apache.org/docs/1.4-M4/adminguide/customising-security.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
