Page Comparison

...

The CONNECT team has collaborated with the NIST team on testing and validating SOAP-based transport for XDR Document Submission and Direct using the NIST's Transport Testing Tool (TTT). This is part of an ongoing effort to ensure that the CONNECT product meets all compliance requirements that are being tested by various certification bodies including NIST. 
 

NIST Transport Edge Testing Tool (httphttps://transport-testingttpedge.nistsitenv.govorg/ttp/ttt#/home)

...

• Download the NIST keystore from http://sourceforge.net/projects/iheos/files/SOAP_TEST.zip/download
• Copy the NIST keystore into key store directory (C:\glassfish3\glassfish\domains\domain1\configCONNECT Properties)
• Export the NIST certificate from keystore as nist.cer

...

Configure Direct

• Import the direct.connectopensource.org mail certificate into cacerts.jks (TTT not set up to communicate with direct direct.connectopensource.net)
• If configdb is not already set up for Direct testing, run PopulateConfigDB-CERTS-anchors.sql
• Download the NIST trust anchor at http://transport-testing.nist.gov/ttt/pubcert/nist.gov.der
• Using AdminGUI, add the trust anchor to the Direct domain

...

Send request from TTT to SUT

1. Browse to http://transport-testing.nist.gov/ttt/
2. Click on XDR Send
3. In Environment dropdown, select SOAP_TEST
4. Enter local patient ID
5. In Select Test Data Set, select anything that has full metadata
6. In SAML dropdown, select NHIN SAML
7. Check the TLS box
8. For Document Recipient, choose the Actor
9. Click Run
10. Click Inspect Results for detailed test results.

...

1. On the Home panel, select the “Simulator Control” in the “Simulators” column
2. In the Environment dropdown, select SOAP_TEST
3. Select “Document Recipient” from the Actor Type pull-down menu.
4. Click “Create Actor Simulator”
5. Copy the End Point Displayed in “PnR TLS endpoint”, this is a TLS endpoint, DO NOT USE the PnR endpoint above it, as it is non-TLS. Note/Copy the TLS endpoint displayed in the page which needs to be updated in the uddiConnectionInfo_g1.xml. The endpoint looks like https://ttt.transport-testing.org:8443/ttt/sim/e6bb0458-ee24-42dc-a003-cb28683e3cd2/rec/xdrpr where the bold characters in the URL is the simulator actor data which will change for each simulator actor we create.
6. Select the Expected C-CDA Type from the list that you will send to the TTT, this will allow the C-CDA to be sent to the appropriate Validator. This endpoint will always be associated with this type C-CDA, you will create an endpoint for each C-CDA you will send. Select Non-CCDA content (no validation) as Expected CCDA Type for XDR content.
7. Enter in the “Name” field the Name you wish to give this connection and save it.
8. Click “Save”, this will create a new simulator under the name you entered above. You can continue to create several connections here, give each a different name to reference later. These names can be referenced in the simulator control messages page for filtering.
9. To leave the “Sim Control” menu up, click “Home”

...

...

Transport Testing Tool User Guide
Transport Testing Tool Configuration (source)