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 "Ruchith Udayanga Fernando (JIRA)" <ji...@apache.org> on 2006/06/12 14:11:30 UTC
[jira] Resolved: (WSS-44) Correct signature confirmation handling
[ http://issues.apache.org/jira/browse/WSS-44?page=all ]
Ruchith Udayanga Fernando resolved WSS-44:
------------------------------------------
Resolution: Fixed
Assign To: Ruchith Udayanga Fernando (was: Davanum Srinivas)
Fixed in the latest SVN
> Correct signature confirmation handling
> ---------------------------------------
>
> Key: WSS-44
> URL: http://issues.apache.org/jira/browse/WSS-44
> Project: WSS4J
> Type: Bug
> Reporter: Michael Pollmeier
> Assignee: Ruchith Udayanga Fernando
>
> As discussed in the mailing list, the signatureConfirmation handling should be reviewed and corrected.
> It seems to be right that the request always contains a signatureConfirmation, even if the request didn't contain a signature (see the spec).
> At the moment the requestor throws an Exception that the response contains a signatureConfirmation but no signatureValue. I agree with Ruchith that we shouldn't throw an exception in this case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org