[prev in list] [next in list] [prev in thread] [next in thread] 

List:       woden-dev
Subject:    [jira] [Comment Edited] (WSS-231) There is an issue with the position of the <Timestamp> element in
From:       "Colm O hEigeartaigh (JIRA)" <jira () apache ! org>
Date:       2012-10-15 8:16:04
Message-ID: 1694359933.44654.1350288964686.JavaMail.jiratomcat () arcas
[Download RAW message or body]


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

Colm O hEigeartaigh edited comment on WSS-231 at 10/15/12 8:15 AM:
-------------------------------------------------------------------


If you want me to help you, you'll need to provide more information. Are you using \
WSS4J 1.5.13-SNAPSHOT? Does it work with WSS4J 1.5.12? Could you attach the message \
that is generated with both WSS4J 1.5.12 and 1.5.13-SNAPSHOT? What web service \
framework are you using with WSS4J? 

Colm.
                
      was (Author: coheigea):
    
If you want me to help you, you'll need to provide more information. Are you using \
WSS4J 1.5.13-SNAPSHOT? Does it work with WSS4J 1.5.12? Could you attack the message \
that is generated with both WSS4J 1.5.12 and 1.5.13-SNAPSHOT? What web service \
framework are you using with WSS4J? 

Colm.
                  
> 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: Colm O hEigeartaigh
> Labels: timestamp, ws-security
> Fix For: 1.5.13, 1.6.8
> 
> 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
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


[prev in list] [next in list] [prev in thread] [next in thread]