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 "Bauer Horscht (JIRA)" <ji...@apache.org> on 2009/09/10 04:59:58 UTC

[jira] Commented: (WSS-208) Signature or decryption was invalid problem when setting WSDoAllSender properties programmatically (Canonicalization / C14N / SAAJ problem ?)

    [ https://issues.apache.org/jira/browse/WSS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753399#action_12753399 ] 

Bauer Horscht commented on WSS-208:
-----------------------------------

I also figured out, that "Signature Encrypt" works fine with both approaches!

No one an idea?

> Signature or decryption was invalid problem when setting WSDoAllSender properties programmatically  (Canonicalization / C14N / SAAJ problem ?)
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WSS-208
>                 URL: https://issues.apache.org/jira/browse/WSS-208
>             Project: WSS4J
>          Issue Type: Test
>          Components: WSS4J Handlers
>    Affects Versions: 1.5.8
>            Reporter: Bauer Horscht
>            Assignee: Ruchith Udayanga Fernando
>            Priority: Blocker
>         Attachments: SignatureFail.zip
>
>
> This test case fails to verify signature, if ("The signature or decryption was invalid... "), in case the WSDoAllSender parameters are set in prefixed handler, whicht sets them as MessageContext properties.
> In case the same parameters are et via a wsdd file on the AxisEngine, the signature verifies.

-- 
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