Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Mon, 18 Apr 2011 12:37:06 +0000 (UTC)
From: "Daniel Kulp (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: 
 <232058246.64225.1303130226192.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <967049409.50308.1302552546281.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CXF-3453) WS-Security signed headers fail when
 schema validation enabled
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CXF-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp updated CXF-3453:
-----------------------------

    Fix Version/s:     (was: 2.4)
                   2.4.1

> WS-Security signed headers fail when schema validation enabled
> --------------------------------------------------------------
>
>                 Key: CXF-3453
>                 URL: https://issues.apache.org/jira/browse/CXF-3453
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.3.1, 2.3.3
>            Reporter: Ross M. Lodge
>            Assignee: Daniel Kulp
>             Fix For: 2.4.1, 2.3.5
>
>         Attachments: SignedHeaderBug.zip
>
>
> After turning on schema validation on a web-service with headers that are signed, but not encrypted, the schema validation fails because the "wsu:Id" is not allowed in the schema.
> I've seen two forms of this:  a complex type header fails with an error saying that the "wsu:Id" attribute isn't allowed, and a simple type header fails saying that no attributes are allowed (except for type, nill, schemaInstance, etc.).
> I think this is a bug, as I don't know anything in the WS-Security specs that would prevent signing of simple type headers or prevent subsequent schema validation.
> I've worked around this by using complex types and adding "<xsd:anyAttribute namespace="##any" processContents="skip"/>" to those types, but it doesn't seem like this should be necessary, and doesn't fix the simple type problem.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira