#614
Account Security
Status:
Open
Priority:
Should have
Milestone:
2.0
Component:
Administration
Assigned To:
Jun 09 2009 * 11:32
Implementation of something like a
- Max. logon attempts before lock
- Max. locks attempts before disable
- Lock duration
- Password pattern
- Days before expiry warning
- Days before expiry
Currently it is possible to hack by trail’n’error without anything like an delay (locking before next possible try).
Comments and Changes
Jun 10 2009 * 07:30
- Assigned user set to Dimitrij Denissenko
- Status changed from Open to Fixed
- Milestone set to 2.0
Jun 11 2009 * 19:45
- Status changed from Fixed to Open
Anonymous
Aug 18 2009 * 15:27
- Component set to Administration
Aug 18 2009 * 23:44
Would you make these options (preferably individually) configurable by the admin panel?
Oct 19 2009 * 20:28
Without wanting to put too much pressure on this – this is the feature which at the time keeps my company from using Retrospectiva in production mode. It is not possible for us to put Retrospectiva up to the Web whilst no significant security measures have been introduced. The above would definitely help.
Oct 20 2009 * 08:02
- Priority changed from Should have to Must have
I already started working on a plugin. I will release a beta as soon as possible.
Anonymous
Dec 15 2009 * 23:08
- Status changed from Open to Fixed
Dec 16 2009 * 13:01
- Status changed from Fixed to Open
Anonymous
Dec 23 2009 * 23:31
- Priority changed from Must have to Critical
Dec 30 2009 * 10:06
- Priority changed from Critical to Should have
This is not a critical priority for 2.0. Account Security will be a plugin anyway.
Powered by 
Feeds