ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nathan Clement <>
Subject RE: WSS4J: Local id attribute and Signature References
Date Mon, 22 Jul 2013 22:59:21 GMT
Hi Colm,

Thanks very much for your response.  Does WSS4J support looking up references by xml:id? 
I'm confused reading the spec as to whether WS-Security requires support for looking up references
by xml:id and local id.  From your response, I'm guessing that the spec only requires support
for wsu:Id?



Date: Mon, 22 Jul 2013 16:11:13 +0100
Subject: Re: WSS4J: Local id attribute and Signature References

Hi Nathan,

I guess this is the kind of scenario that you should plug in your own CallbackLookup implementation.
You can set one on the WSSecurityEngine implementation used as the starting point for WS-Security


On Fri, Jul 19, 2013 at 1:37 AM, Nathan Clement <> wrote:


The WS-Security spec says in section 4 "ID References":

However, because some key schemas used by this specification don't allow attribute extensibility
(namely XML Signature and XML Encryption), this specification also allows use of their local
ID attributes in addition to the wsu:Id attribute and the xml:id attribute [XMLID]

We are attempting to process an AS4 message, and the AS4 spec (
says in section 5.1.4 regarding the signature reference for the eb:Messaging header:

The eb:Messaging header SHOULD be referenced using the “id”

WSS4J doesn't seem to support looking up referenced elements by a local id attribute.  DOMCallbackLookup
calls WSSecurityUtil.findElementById which only looks for wsu:Id or Id (with a capital I)
with no namespace.

Should WSS4J allow lookup of a signed element by local id attribute?


<eb:Messaging s:mustUnderstand="true" id="ebms_header" ...

<ds:Signature xmlns:ds="">

    <ds:Reference URI="#ebms_header">




Colm O hEigeartaigh

Talend Community Coder
View raw message