]
Shane Bryzak closed JBSEAM-3502.
--------------------------------
Fix Version/s: 2.1.0.GA
Resolution: Done
Assignee: Shane Bryzak
Fixed in SVN.
Make
org.jboss.seam.security.management.JpaIdentityStore.generatePasswordHash() protected
instead of private.
-------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3502
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3502
Project: Seam
Issue Type: Bug
Components: Security
Affects Versions: 2.1.0.CR1
Reporter: Stephan Kleine
Assignee: Shane Bryzak
Fix For: 2.1.0.GA
Original Estimate: 1 minute
Remaining Estimate: 1 minute
I really like the updated security model and would love to use your JpaIdentityStore
implementation but since I use Jasypt (
http://www.jasypt.org/ ) to handle my passwords I
have to adapt it a bit.
As far as I can see the easiest way would be to subclass your JpaIdentityStore
implementation and override generatePasswordHash() and authenticate() - the rest should
work just fine out of the box. But, since generatePasswordHash() is private, I would have
to override more methods just to redirect the generatePasswordHash() calls which I would
like to avoid.
So please make org.jboss.seam.security.management.JpaIdentityStore.generatePasswordHash()
protected because it makes the security model more customizable, like for situations
described above, without compromising security.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: