W3C home > Mailing lists > Public > www-xkms@w3.org > September 2007

XKMS 2.0 Errata - WSDL / Pass Phrase Computation

From: Silvan Krebs <silvan.krebs@gmail.com>
Date: Fri, 14 Sep 2007 15:54:53 +0200
Message-ID: <9538027f0709140654t54ee172q6eb9461cde5ff944@mail.gmail.com>
To: www-xkms@w3.org
Dear all,

We are two students (Silvan Krebs and Sebastian Fiechter) from Bern
University of Appliced Sciences working currently on our diploma thesis
about Xml Key Management Specification 2.
The subject of our diploma thesis is an opensource implementation of the
XKMS 2.0. In the past few months, we developed a web service and a client
API, fully XKMS 2.0 compliant, using JAX-WS RI 2.1.1 and Java 6. Our project
is called OpenXKMS.

However, during the implementation of our XKMS system, we came across
following guidelines that were not very obvious to us:

Errata xkms.wsdl

Because the provided xkms.wsdl (http://www.w3.org/TR/xkms2/Schemas/xkms.wsdl )
cannot be parsed in context of Xalan, JAX-B and JAX-WS, we had to apply some
changes to it:

1. Remove all 'message' attributes from the tags named 'input' and 'output'
(was not schema-compliant before).

2. Replace '&soapaction;' by a concrete action header or nothing.

3. Replace

 <wsdlsoap:address location="&serviceURL;"/>


 <wsdlsoap:address location="REPLACE_WITH_ACTUAL_URL" />

or the concrete service url.

4. Remove the inline DTD:

 	<!DOCTYPE wsdl:definitions [ 	
 	  <!ENTITY tns 'http://www.w3.org/2002/03/xkms#wsdl'
 	  <!ENTITY schemaURL 'http://www.w3.org/TR/xkms2/Schemas/xkms.xsd'
 	  <!ENTITY soapaction *>*
 	  <!ENTITY serviceURL 'http://xkms.example.com/xkms/2'

5. Complete the '<wsdl:definitions' element with the following namespaces
(replace last line with your own ws namespace):


6. Replace the following schema import

 <import namespace="http://www.w3.org/2002/03/xkms#"


           <xsd:import namespace="http://www.w3.org/2002/03/xkms#"


You'll find the complete adapted xkms.wsdl on

Errata XKMS 2.0

Type: Editorial

Refers to: XKMS 2.0 Specification, chapter: "C.2 Pass Phrase Computation" p.
Description: Reads twice (in both examples C.2.1 and C.2.2): "Pass Phrase
Pass 1 HMAC-SHA1 (Converted Authentication Data, 0x2)"

Correction: It should read: "Pass Phrase Pass 1 HMAC-SHA1 (Converted *Pass
Phrase*, 0x2)"

It would be glad if you could give us a quick response to ensure we are
right with our corrections to XKMS 2.0 (especially for the Pass Phrase

Further, we are currently finishing our first release (approximately in
November this year). To be able to test the whole implementation (client and
web service), it would be glad if you could give us some contacts of parties
that have already developed a XKM System (XKMS 2.0 compliant) as we are
forcing now peer application tests.

Thanks in advance!

Best regards,
Silvan Krebs
Sebastian Fiechter
Received on Friday, 14 September 2007 14:34:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:31:44 UTC