Mikolaj: How are you creating the document on the client side (signing time)?
I have found that when I create a dom through straight JAXP/xerces and send it to a JAXM service that the namespaces vanish. I was then adding the namespace in on the server side so that verification would succeed. This was admittedly a hack. When I switched to building the soap request via the JAXM javax.xml.soap/messaging classes the canonicalized form on the client side matched that on the server side. I still don't understand why it doesn't propagate the namespace down to the signedInfo element but at least the signature verifies. So turns out - reading the xml file from disk pulling out an element to sign and expecting it to be verified on server side ended up being a poor assumption. I hope this is somehow helpful for your situation. --larry > -----Original Message----- > From: Mikolaj Habryn [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 15, 2004 9:24 AM > To: [EMAIL PROTECTED] > Subject: Re: vanishing attribute namespace prefixes redux > > > On Wed, 2004-09-15 at 22:59, Mikolaj Habryn wrote: > > What am I missing here? There must be something blindingly > obvious :( > > And just as a final note, if I rely purely on createElementNS (ie, no > setAttributeNS(..."xmlns"...) stuff), dump the DOM to a > string and reparse it from scratch before handing it off to > XMLSignature, it works. Which is to say, it doesn't bomb > mysteriously in the depths somewhere, but the signatures > don't validate. > > m. > > > -- > This message has been scanned for viruses and > dangerous content, and is believed to be clean. > -- This message has been scanned for viruses and dangerous content, and is believed to be clean.
