[
https://issues.apache.org/jira/browse/WSS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493866#comment-13493866
]
Colm O hEigeartaigh commented on WSS-355:
-----------------------------------------
Hi Marc,
The original issue was that the WSS4J 1.6.x code did not use any signing
functionality in SAMLCallback. If both sets of code are now consistent then
this issue can be resolved.
I think it's ok to have separate Callbacks in the test code - I'll leave it up
to you whether you want to refactor it or not.
Colm.
> Reconcile SAMLCallback between the two implementations
> ------------------------------------------------------
>
> Key: WSS-355
> URL: https://issues.apache.org/jira/browse/WSS-355
> Project: WSS4J
> Issue Type: Sub-task
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Fix For: 2.0
>
>
> The SAMLCallback in SWSSF contains signing information, whereas it does not
> in WSS4J. SAMLParms and SAMLIssuer* will be removed in the DOM code as part
> of this work.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
