[
https://issues.apache.org/jira/browse/WSS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931073#action_12931073
]
Colm O hEigeartaigh commented on WSS-208:
-----------------------------------------
I took another look at this issue. The problem is that for your dynamic
configuration approach, the global configuration option "disablePrettyXML" is
set to false (by default), and that explains the indentation on the SOAP body
above, which was causing signature verification to fail on the server side.
To fix this, replace the following line in your LaunchClient.java:
service.setEngine(new AxisClient(eng));
with:
AxisClient client = new AxisClient(eng);
client.setOption(AxisClient.PROP_DISABLE_PRETTY_XML, Boolean.TRUE);
service.setEngine(client);
and it works fine.
I'm marking this as won't fix.
Colm.
> 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: Colm O hEigeartaigh
> 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: [email protected]
For additional commands, e-mail: [email protected]
