Closed glassfishrobot closed 12 years ago
Reported by elduff@java.net
elduff@java.net said: Created an attachment (id=1175) SOAP response
elduff@java.net said: Created an attachment (id=1176) SOAP request
elduff@java.net said: Created an attachment (id=1177) full stack trace
m_potociar@java.net said: Moving to security subcomponent
sm228678@java.net said: Hi, can you attach the WSE service wsdl to reproduce the issue? is there a direcy way to reproduce the error on our side? Thanks
sm228678@java.net said: can you please send the wsdl of the WSE 3.0 .NET web service? we want to reproduce the issue on our side !! thanks suresh
sm228678@java.net said: need a reproducible test case from user
File: request.xml Attached By: elduff@java.net
File: response.xml Attached By: elduff@java.net
File: stackTrace_05032010.txt Attached By: elduff@java.net
Was assigned to snajper
This issue was imported from java.net JIRA WSIT-1423
Marked as incomplete on Friday, October 12th 2012, 4:40:13 am
I have been working on writing a Metro client that will call a WSE 3.0 .NET web service. That web service is protected by MutualCerticate10 security, with secure conversation & signature encryption turned off. Essentially, we are just encrypting the header & body of the message & signing the headers. I am able to send a request to the service & they can process it and send a response. However, the WSIT code is failing when trying to process the response.
The exception is being thrown from this code in:
com.sun.xml.ws.security.opt.impl.incoming.GenericSecuredHeader:
private XMLStreamBuffer completeHeader; public void writeTo(XMLStreamWriter w) throws XMLStreamException { try { // TODO what about in-scope namespaces completeHeader.writeToXMLStreamWriter(w); } catch (Exception e) { throw new XMLStreamException(e); } }
Note the 'TODO' in that code snippet. I'm not sure exactly what is meant by 'in-scope namespaces', but I think that may be the situation I have.
Here's a snippet from the WSE 3.0 response that WSIT/StreamBuffer is failing on. If I'm understanding correctly, Metro is failing because the 'Reference' element & its children don't explicity state what namespace they're in. It seems that Metro/StreamBuffer does not support inheriting the namespace from the parent 'Signature' element.