#10959: API for password validation policy
---------------------+------------------------------------------------------
 Reporter:  djay     |        Owner:     
     Type:  PLIP     |       Status:  new
 Priority:  minor    |    Milestone:  4.1
Component:  Unknown  |   Resolution:     
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by djay):

 Replying to [comment:5 ggozad]:
 > I had done some work for ENISA on a generic password policy product that
 would do password complexity, aging and expiration as well as keep a
 password history so that the same password is not reused. Let me know if
 you need help I would be happy to adapt it and contribute.

 I'd love to discuss this. Please contact me. The scope of this PLIP is
 just to put in place hooks to make it easy to put in 3rd party plugins
 with validation rules. That would cover password complexity and history
 but wouldn't handle expiration and aging. Did it involve patching core
 code to enable aging and expiration?

-- 
Ticket URL: <http://dev.plone.org/plone/ticket/10959#comment:9>
Plone <http://plone.org>
Plone Content Management System
_______________________________________________
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories

Reply via email to