[MAGNOLIA-1730] Introduce password generation and password matching strategies Created: 07/Sep/07  Updated: 06/Jan/14  Resolved: 06/Jan/14

Status: Closed
Project: Magnolia
Component/s: core, security
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Neutral
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Won't Fix Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Comments   
Comment by Magnolia International [ 06/Jan/14 ]

Since we changed to using encryption a loooong time ago, this isn't very relevant anymore.
This would only make sense if we ever rewrite the entire sec/auth framework, which would be better delegating to a good library (such as Shiro); it'd then make sense, since we'd want to support different users stores, which could each have their own password gen/match implementations.

Generated at Mon Feb 12 03:29:46 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.