You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ws.apache.org by "Marc Giger (JIRA)" <ji...@apache.org> on 2012/11/09 12:00:12 UTC

[jira] [Resolved] (WSS-356) Investigate signing Crypto differences

     [ https://issues.apache.org/jira/browse/WSS-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marc Giger resolved WSS-356.
----------------------------

    Resolution: Not A Problem
      Assignee: Marc Giger  (was: Colm O hEigeartaigh)

Hi Colm,

Both implementation do behave the same way. Therefore will mark this issue as resolved.

Marc
                
> Investigate signing Crypto differences
> --------------------------------------
>
>                 Key: WSS-356
>                 URL: https://issues.apache.org/jira/browse/WSS-356
>             Project: WSS4J
>          Issue Type: Sub-task
>            Reporter: Colm O hEigeartaigh
>            Assignee: Marc Giger
>             Fix For: 2.0
>
>
> Is there really a need to have a separate Crypto instance to sign SAML Assertions? Maybe we should just use the signature Crypto instance for this instead?

--
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: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org