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

Posted to dev@ws.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2011/02/10 13:42:57 UTC

[jira] Resolved: (WSS-270) No need to ensure Crypto object is non-null for SAML signature verification using a secret key

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

Colm O hEigeartaigh resolved WSS-270.
-------------------------------------

    Resolution: Fixed

> No need to ensure Crypto object is non-null for SAML signature verification using a secret key
> ----------------------------------------------------------------------------------------------
>
>                 Key: WSS-270
>                 URL: https://issues.apache.org/jira/browse/WSS-270
>             Project: WSS4J
>          Issue Type: Bug
>    Affects Versions: 1.5.11
>            Reporter: Colm O hEigeartaigh
>            Assignee: Colm O hEigeartaigh
>             Fix For: 1.6, 1.5.12
>
>
> WSS4J currently throws an Exception if the Crypto object is non-null when trying to verify a signature, where the KeyInfo of the signature points to a SAML Assertion. However, for certain cases we query the CallbackHandler for a key, and so the check on Crypto can be delayed.

-- 
This message is automatically generated by JIRA.
-
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