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 3C6C7200C82 for ; Fri, 12 May 2017 14:07:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 39F81160BC8; Fri, 12 May 2017 12:07:10 +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 90251160BA3 for ; Fri, 12 May 2017 14:07:09 +0200 (CEST) Received: (qmail 16633 invoked by uid 500); 12 May 2017 12:07:08 -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 16607 invoked by uid 99); 12 May 2017 12:07:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 May 2017 12:07:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 2C4F4C0145 for ; Fri, 12 May 2017 12:07:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.201 X-Spam-Level: X-Spam-Status: No, score=-99.201 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id le6_aOeA-Zuu for ; Fri, 12 May 2017 12:07:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 9F0F25FDC0 for ; Fri, 12 May 2017 12:07:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C2400E0D56 for ; Fri, 12 May 2017 12:07:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2B1F424303 for ; Fri, 12 May 2017 12:07:04 +0000 (UTC) Date: Fri, 12 May 2017 12:07:04 +0000 (UTC) From: "Colm O hEigeartaigh (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CXF-7369) Signed element with an attribute named Id leaves a WSS Id attribute in the response MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 12 May 2017 12:07:10 -0000 [ https://issues.apache.org/jira/browse/CXF-7369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008025#comment-16008025 ] Colm O hEigeartaigh commented on CXF-7369: ------------------------------------------ The sending system is allowed add the wsu:Id attribute yes. The consumer system needs to remove the wsu:Id if it is doing schema validation. We can't remove it by default in case it was added prior to the signature creation process and causes some reference to fail. > Signed element with an attribute named Id leaves a WSS Id attribute in the response > ------------------------------------------------------------------------------------ > > Key: CXF-7369 > URL: https://issues.apache.org/jira/browse/CXF-7369 > Project: CXF > Issue Type: Bug > Components: WS-* Components > Affects Versions: 3.1.8, 3.1.11 > Environment: Weblogic 12.1 > Java 1.8.0_121 > RedHat Linux > Reporter: Cullen Davis > > Setup: > Create a Soap service that has a WssRequiredSignatureHandler. > Create an XML Element that has an attribute named id. > Create a soap request that uses the element with the id attribute > Specify that body be of the Soap request be a WSS Signed Element. > Invoke the Soap service method. > Expected Result > The SOAP response will have an element with a single id attribute > Actual Result: > The SOAP response will have an element with a expected id attribute as well as an extra wsu:Id attribute. wsu maps to http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd > Work Around > Rename the attribute. -- This message was sent by Atlassian JIRA (v6.3.15#6346)