[
https://issues.apache.org/jira/browse/JSPWIKI-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18140431#comment-18140431
]
ASF subversion and git services commented on JSPWIKI-1254:
----------------------------------------------------------
Commit c0689fbf2cefc3dc3411c183f00c9cc7832b1f31 in jspwiki's branch
refs/heads/master from Arturo Bernal
[ https://gitbox.apache.org/repos/asf?p=jspwiki.git;h=c0689fbf2 ]
JSPWIKI-1254 Make the lock of a user profile work
A user profile can be locked until a date, but nothing made use of it:
- UserDatabaseLoginModule never looked at the lock, so a locked profile could
log in. It now refuses a locked profile that supplies the right password with
an
AccountLockedException. With a wrong password the failure is the usual one, so
the lock is not disclosed to someone who does not know the password.
- XMLUserDatabase wrote the lock expiry in its date format but read it with
Long.parseLong, so a saved lock made the profile unreadable with a
NumberFormatException. It now reads the date format, still accepts
milliseconds,
and keeps the profile locked if the value cannot be read.
- JDBCUserDatabase stored the lock expiry as a date, without the time, so a lock
of an hour ended at midnight of the day it was set and the profile was not
locked
when read back. It now stores a timestamp.
This is needed before locking accounts automatically.
> Support password expiration, password change reminders and account automatic
> lockout and eventual deletion
> ----------------------------------------------------------------------------------------------------------
>
> Key: JSPWIKI-1254
> URL: https://issues.apache.org/jira/browse/JSPWIKI-1254
> Project: JSPWiki
> Issue Type: New Feature
> Reporter: Alex O'Ree
> Assignee: Alex O'Ree
> Priority: Major
> Labels: pull-request-available
>
> applies to all wiki based authenticators (xml and jdbc database providers)
> all opt in features of course.
> after V days, dispatch an email that the password will expire soon,
> after X days, require a password change at login
> after Y days, lock an account from logins entirely, dispatching an email
> along with a warning of account deletion. to unlock, administrative
> intervention is required
> after Z days, delete an account permanently, dispatching an email
> after a period of W days without login and a new login is detected, dispatch
> an email to the account owner to confirm login
> and we'll probably need an admin tool for some of this
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)