- From: Stefan Lischke <lischke@googlemail.com>
- Date: Fri, 14 Sep 2007 17:32:49 +0200
- To: Silvan Krebs <silvan.krebs@gmail.com>
- CC: www-xkms@w3.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, why do you guys want to reinvent the wheel? a wonderful opensource implementation was already done by some portugese students for there thesis. Have a look at: http://sourceforge.net/projects/xkms/ before answering your wsdl questions, which tool you used to create your WS-implementation ? Axis2? or any other stefan Silvan Krebs wrote: > 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;"/> > > by > > <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' > <http://www.w3.org/2002/03/xkms#wsdl%27>> > <!ENTITY schemaURL 'http://www.w3.org/TR/xkms2/Schemas/xkms.xsd' > <http://www.w3.org/TR/xkms2/Schemas/xkms.xsd%27>> > <!ENTITY soapaction *>* > <!ENTITY serviceURL 'http://xkms.example.com/xkms/2' > <http://xkms.example.com/xkms/2%27>> > ]> > > 5. Complete the '<wsdl:definitions' element with the following namespaces > (replace last line with your own ws namespace): > > xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" > xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" > xmlns:xsd="http://www.w3.org/2001/XMLSchema" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:ws="http://www.example.org/openxkms2" > > 6. Replace the following schema import > > <import namespace="http://www.w3.org/2002/03/xkms#" > location='http://www.w3.org/TR/xkms2/Schemas/xkms.xsd'/ > <http://www.w3.org/TR/xkms2/Schemas/xkms.xsd%27/>> > > by > > <types> > <xsd:schema> > <xsd:import namespace="http://www.w3.org/2002/03/xkms#" > > schemaLocation="http://www.w3.org/TR/xkms2/Schemas/xkms.xsd"/> > </xsd:schema> > </types> > > > You'll find the complete adapted xkms.wsdl on > http://www.openxkms.net/intranet/wiki/index.php/Projectdoc_Anhaenge_Errata#OpenXKMS2_adapted_xkms.wsdl > > > Errata XKMS 2.0 > > Type: Editorial > > Refers to: XKMS 2.0 Specification, chapter: "C.2 Pass Phrase Computation" p. > [386] > 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 > Computation). > > 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 > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG6qmhL5hrdXRZQD8RAk33AJ9+NRfAWxwFxJJZ2YX44m6lmWSvBACfQHzj ttqdLPEi+JrKareOsBU+oZM= =mWpq -----END PGP SIGNATURE-----
Received on Friday, 14 September 2007 15:34:05 UTC