XDR Test 3 Failure

[Pepper Pancoast]

We're getting a failure for our address on XDR Test 3 with our endpoint being https://medallies.netsmartcloud.com/DocumentRecipientPort/DocumentRecipient

The debugging info shows  

Exception: a problem occured while sending the XDR document

Caused by:

Requesting: xdr 

and the logs are showing no content.  I just tried it locally from Postman and was able to make a successful connection.  Do you have a way to provide more details on the failure?

[Kim Poletti]

Hi - Thanks for reaching out. This has been logged for review and a member of the team will reach out in the near future.

[Pepper Pancoast]

Thanks!  Any chance we'd get some feedback today?  We're prepping for our certification.

[Sai Valluripalli]

I see you are using https endpoint, for https you have to replace your certs with ETT certs provided by the tool.

Alternatively, you can use http endpoint if your system supports it

--
You received this message because you are subscribed to the Google Groups "Edge Test Tool (ETT)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to edge-test-too...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/153178ec-d969-46eb-aff4-88468c526c1cn%40googlegroups.com.

[Pepper Pancoast]

Thanks for the context! I just confirmed that we are exposing your cert on our endpoint and still getting an error.

[Sai Valluripalli]

The reason is -

X-REASON: XdsFormat error Request was MTOM format but response was SIMPLE SOAP
4 < X-STACK-TRACE1: Request was MTOM format but response was SIMPLE SOAP

The response must be in MTOM format

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/e123400b-2cd7-41ed-bd5c-95f86ce8ae9en%40googlegroups.com.

[Pepper Pancoast]

Curious, we're just returning a success, there's not really a document or binary attached.

HTTP/1.1 200 OK

Date: Tue, 04 Jun 2024 15:29:00 GMT

Transfer-Encoding: chunked

Content-Type: application/soap+xml; charset=utf-8

 

<?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope" xmlns:S="http://www.w3.org/2003/05/soap-envelope"><env:Header><Action xmlns="http://www.w3.org/2005/08/addressing" S:mustUnderstand="1">urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-bResponse</Action><RelatesTo xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:AD26219DC8B723A59C1717514940308</RelatesTo><work:WorkContext xmlns:work="http://oracle.com/weblogic/soap/workarea/">rO0ABXdjACN3ZWJsb2dpYy5hcHAuQ2FyZUNvbm5lY3RJbmJveFdTLWVhcgAAANYAAAAjd2VibG9naWMud29ya2FyZWEuU3RyaW5nV29ya0NvbnRleHQADzEuMi4zNC1TTkFQU0hPVAAA</work:WorkContext></env:Header><S:Body><ns1:RegistryResponse xmlns:ns1="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success"/></S:Body></S:Envelope>

Here's our response, why do we need to MTOM encode the response?

[Sai Valluripalli]

Content-Type: application/soap+xml; charset=utf-8 indicates this is not MTOM.

Please refer here as to why it should be MTOM - 

https://www.healthit.gov/test-method/direct-project-edge-protocol-and-xdrxdm

https://wiki.directproject.org/wiki/File:2011-03-09_PDF_-_XDR_and_XDM_for_Direct_Messaging_Specification_FINAL.pdf

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/763bc8eb-a547-463b-9939-e2cc0be5fe77n%40googlegroups.com.

[Pepper Pancoast]

Thank you, we got it resolved :)

[Kim Poletti]

Thank you. We will close this ticket.