[
https://issues.apache.org/jira/browse/WSS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved WSS-170.
-------------------------------------
Resolution: Fixed
> SignatureAction does not set DigestAlgorithm on WSSecSignature instance
> -----------------------------------------------------------------------
>
> Key: WSS-170
> URL: https://issues.apache.org/jira/browse/WSS-170
> Project: WSS4J
> Issue Type: Improvement
> Components: WSS4J Core
> Affects Versions: 1.5.6
> Reporter: Rik Gruwez
> Assignee: Colm O hEigeartaigh
> Fix For: 1.5.7, 1.6
>
> Attachments: WSS4J.txt
>
>
> Right now the SignatureAction.executre() method does not explicitely set the
> digest algorithm. As a result the Algorithm attribute of the Soap message's
> DigestMethod tag will always contain the SHA1 URI, even though you are using
> RSA-SHA256 for the signature. If I add these lines to the execute() method of
> the SignatureAction, it works for me:
> if (reqData.getDigestAlgorithm()!=null)
> wsSign.setDigestAlgo(reqData.getDigestAlgorithm());
> Obviously, I also had to add a digestMethod field to the RequestData class in
> order to make it work.
--
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]
