Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
ID | |||||||||||
0003416 | |||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
feature request | [Openbravo ERP] C. Security | minor | always | 2007-11-16 19:51 | 2013-08-05 08:55 | ||||||
Reporter | plujan | View Status | public | ||||||||
Assigned To | iciordia | ||||||||||
Priority | normal | Resolution | open | Fixed in Version | |||||||
Status | acknowledged | Fix in branch | Fixed in SCM revision | ||||||||
Projection | none | ETA | none | Target Version | |||||||
OS | Any | Database | Any | Java version | |||||||
OS Version | Database version | Ant version | |||||||||
Product Version | SCM revision | ||||||||||
Review Assigned To | |||||||||||
Web browser | |||||||||||
Modules | Core | ||||||||||
Regression level | |||||||||||
Regression date | |||||||||||
Regression introduced in release | |||||||||||
Regression introduced by commit | |||||||||||
Triggers an Emergency Pack | No | ||||||||||
Summary | 0003416: Openbravo should provide password policies support | ||||||||||
Description | There are some best practices about passwords that should be considered as part of Openbravo standard. * Maximun Password length: Now is limited to 10 chars by GUI, it should be extended to 20 to allow stronger passwords * Minimun Password length: A password should not have less than 7 chars * Expiration: Passwords should expire after a defined period of time * Password history: Users should not change a password to a used recently one * Password complexity: A strong password has uppercase and lowercase as well as numbers, it would be great is change password window check that. Additionally, a password lockout when trying to access N times sometimes helps (while many times just mess it up) | ||||||||||
Tags | No tags attached. | ||||||||||
Attached Files | |||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | ||||||||
|
Notes | |
(0003922) villind (developer) 2007-11-19 13:02 edited on: 2008-06-12 09:26 |
Logged In: YES user_id=61737 Originator: NO I would vote for http://sourceforge.net/tracker/index.php?func=detail&aid=1833751&group_id=162271&atid=823132 [^] instead of this. It is more important to provide means for strong authentication than implementing it. I would not see that there would be sense to support smart cards or 3factor authentication in Openbravo directly, bu enable integration with such solutions. |
(0007005) user71 2005-06-01 00:00 edited on: 2008-06-12 09:44 |
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis. You can see the original bug report in: https://sourceforge.net/support/tracker.php?aid=1833307 [^] |
Issue History | |||
Date Modified | Username | Field | Change |
2008-06-30 19:50 | pjuvara | Status | new => acknowledged |
2008-06-30 19:50 | pjuvara | Relationship added | blocks 0000500 |
2008-11-16 07:44 | pjuvara | Assigned To | alostale => pjuvara |
2009-05-22 19:36 | pjuvara | Assigned To | pjuvara => iciordia |
2009-09-01 09:14 | roklenardic | Relationship added | blocks 0010399 |
2013-08-05 08:55 | mmarquez | Issue Monitored: mmarquez |
Copyright © 2000 - 2009 MantisBT Group |