You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Kevin T (Commented) (JIRA)" <ji...@apache.org> on 2012/03/01 23:39:00 UTC
[jira] [Commented] (WSS-231) There is an issue with the position of
the element in the header when using WSS4J calling
.NET Web Services with WS-Security.
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220440#comment-13220440 ]
Kevin T commented on WSS-231:
-----------------------------
Abd K, I am coming across this issue too. I went and got the WSSecSignature.java file off of the 1.5.10 branch and tried to run the patch file you attached, but it fails with the following error:
patching file WSSecSignature.java
patching file WSSecSignature.java
Hunk #1 FAILED at 129.
1 out of 1 hunk FAILED -- saving rejects to file WSSecSignature.java.rej
patching file WSSecSignature.java
Hunk #1 FAILED at 717.
1 out of 1 hunk FAILED -- saving rejects to file WSSecSignature.java.rej
patching file WSSecSignature.java
Hunk #1 FAILED at 101.
1 out of 1 hunk FAILED -- saving rejects to file WSSecSignature.java.rej
Is there anyway you can attach the modified WSSecSignature class instead of just the patch?
> There is an issue with the position of the <Timestamp> element in the <Security> header when using WSS4J calling .NET Web Services with WS-Security.
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WSS-231
> URL: https://issues.apache.org/jira/browse/WSS-231
> Project: WSS4J
> Issue Type: Bug
> Components: WSS4J Core
> Affects Versions: 1.5.8
> Environment: Windows, Solaris
> Reporter: Chris Weitner
> Assignee: Ruchith Udayanga Fernando
> Labels: timestamp, ws-security
> Attachments: patch.txt
>
>
> There is an issue with the position of the <Timestamp> element in the <Security> header when using WSS4J calling .NET Web Services with WS-Security. When using the "Timestamp Signature" action over https, we are receiving the following error: "Signing without primary signature requires timestamp". When I modified org.apache.ws.security.message.WSSecSignature to position <Timestamp> as the first element in <Security> it worked fine (by default <Timestamp> is the last element and after the <Signature>). Can this be fixed or can you make Timestamp positioned first as a configuration option?
> <soapenv:Header>
> <wsse:Security>
>
> <wsu:Timestamp>
> <wsu:Created>2010-05-06T16:46:31.594Z</wsu:Created>
> <wsu:Expires>2010-05-06T16:51:31.594Z</wsu:Expires>
> </wsu:Timestamp>
>
> <wsse:BinarySecurityToken</wsse:BinarySecurityToken>
>
> <ds:Signature>
> ....
> </ds:Signature>
> </wsse:Security>
> </soapenv:Header>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org