1) Reused your solution for the default and custom SecureRandomProvider. Which some small changes.
2) Users can now specify the algorithm and key length to the PasswordCredentialHandler.
3) Users can now specify a time interval to get the SecureRandom updated.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
@Marek,
I have pushed some code to a branch considering what we discussed:
https://github.com/pedroigor/picketlink/commit/7bf0448d3bbaf67b3733fcfda866508b0e6d486a
Some highlights:
1) Reused your solution for the default and custom SecureRandomProvider. Which some small changes.
2) Users can now specify the algorithm and key length to the PasswordCredentialHandler.
3) Users can now specify a time interval to get the SecureRandom updated.