Return-Path: X-Original-To: apmail-ws-dev-archive@www.apache.org Delivered-To: apmail-ws-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E6A71DA03 for ; Wed, 5 Sep 2012 14:14:08 +0000 (UTC) Received: (qmail 14150 invoked by uid 500); 5 Sep 2012 14:14:08 -0000 Delivered-To: apmail-ws-dev-archive@ws.apache.org Received: (qmail 13938 invoked by uid 500); 5 Sep 2012 14:14:08 -0000 Mailing-List: contact dev-help@ws.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ws.apache.org Delivered-To: mailing list dev@ws.apache.org Received: (qmail 13930 invoked by uid 99); 5 Sep 2012 14:14:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Sep 2012 14:14:08 +0000 Date: Thu, 6 Sep 2012 01:14:08 +1100 (NCT) From: "nag (JIRA)" To: dev@ws.apache.org Message-ID: <242270971.39082.1346854448077.JavaMail.jiratomcat@arcas> Subject: [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. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448764#comment-13448764 ] nag commented on WSS-231: ------------------------- When I switch the actions to Signature Timestamp I am getting this error? org.apache.ws.security.WSSecurityException: General security error (WSEncryptBody/WSSignEnvelope: Element to encrypt/sign not found: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd, Timestamp); nested exception is org.apache.ws.security.WSSecurityException: Error during Signature: ; nested exception is: org.apache.ws.security.WSSecurityException: General security error (WSEncryptBody/WSSignEnvelope: Element to encrypt/sign not found: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd, Timestamp) > There is an issue with the position of the element in the 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.6.8 > > Attachments: patch.txt > > > There is an issue with the position of the element in the 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 as the first element in it worked fine (by default is the last element and after the ). Can this be fixed or can you make Timestamp positioned first as a configuration option? > > > > > 2010-05-06T16:46:31.594Z > 2010-05-06T16:51:31.594Z > > > > > > .... > > > -- 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