Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A5451200B33 for ; Tue, 24 May 2016 15:14:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A3FFA160A35; Tue, 24 May 2016 13:14:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E57F6160A36 for ; Tue, 24 May 2016 15:14:13 +0200 (CEST) Received: (qmail 56366 invoked by uid 500); 24 May 2016 13:14:13 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 56193 invoked by uid 99); 24 May 2016 13:14:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 May 2016 13:14:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D771B2C1F5D for ; Tue, 24 May 2016 13:14:12 +0000 (UTC) Date: Tue, 24 May 2016 13:14:12 +0000 (UTC) From: "Colm O hEigeartaigh (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CXF-6900) invalid signature in case of soap fault MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 24 May 2016 13:14:14 -0000 [ https://issues.apache.org/jira/browse/CXF-6900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298149#comment-15298149 ] Colm O hEigeartaigh commented on CXF-6900: ------------------------------------------ Hi David, The problem here is actually a problem with the SAAJ implementation that comes with the JDK, where it "forces" the "env" prefix for a SOAP Fault when it does not have a pre-existing prefix. [~dkulp] and I have managed to "work around" this problem in CXF. Your test-case should now be working on the CXF master + 3.1.x-fixes branch. However, I believe it won't be backported to CXF 3.0.x, as there are too many changes involved. Colm. > invalid signature in case of soap fault > --------------------------------------- > > Key: CXF-6900 > URL: https://issues.apache.org/jira/browse/CXF-6900 > Project: CXF > Issue Type: Bug > Components: WS-* Components > Affects Versions: 3.0.3 > Environment: windows 2008 jdk 1.6.0_45 > Reporter: david leruse > Assignee: Colm O hEigeartaigh > Fix For: 3.1.7 > > Attachments: server7.log > > > Hello, > Having signature verification problems on the cxf client-side with a .NET Ws-fed protected webservice, I ask you a little help... > Here is a summary of the problem : > Most of the time, communication works well excepted when we got a soap fault message. > Indeed signature validation works usually well excepted when > we receive a fault message inside the body of the soap message. Even In this boundary case, signature verification works well excepted for one element, the fault message (see the enclosed server7.log file). > After digging a bit, i've found that the calculated digest couldn't be equal to the claimed one because the content of the message given to the DigesterOutpustrream is not well canonicalized or normalized. > Partial decrypted msg > ... > > DataNotFoundFaultContextContactInfo with Id '1' does not exist.ContextContactInfoNotFoundContextContactInfo with Id '1' does not exist. > > ... > Predigested input : > DataNotFoundFaultContextContactInfo with Id '1' does not exist.ContextContactInfoNotFoundContextContactInfo with Id '1' does not exist. > Could you please check this problem and give me an advice ? > The library used are : > cxf 3.0.3 > wss4j 2.0.2 > xmlsec 2.0.2 > on a jdk 1.6.0_45 > Thanks in advance > David L -- This message was sent by Atlassian JIRA (v6.3.4#6332)