You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wss4j-dev@ws.apache.org by "David Valeri (JIRA)" <ji...@apache.org> on 2010/01/15 22:44:54 UTC

[jira] Updated: (WSS-224) SAMLTokenSignedAction and WSSecSignatureSAML do not honor signature algorithm or digest algorithm from WSSHandler configuration

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

David Valeri updated WSS-224:
-----------------------------

    Attachment: patch.txt

A patch that resolves the issue and adds a rudimentary exercising of the code.  The test case lacks confirmation that the settings were honored by WSSecSignatureSAML .

> SAMLTokenSignedAction and  WSSecSignatureSAML do not honor signature algorithm or digest algorithm from WSSHandler configuration
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WSS-224
>                 URL: https://issues.apache.org/jira/browse/WSS-224
>             Project: WSS4J
>          Issue Type: Bug
>          Components: WSS4J Core
>    Affects Versions: 1.5.8, 1.5.9
>            Reporter: David Valeri
>            Assignee: Ruchith Udayanga Fernando
>         Attachments: patch.txt
>
>
> If these configuration options are set in the WSSHandler config, they are transposed to the RequestData, but the action ignores them.  If one changes the action to set them on WSSecSignatureSAML, the digest algorithm is not taken into account when addReferencesToSign creates the signature references.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org