<H3>Special Instructions</H3> <p>Your ATNA Secure Node or Secure Application may not support the HTTP protocol. In that case, skip this test</p> <p>The documentation in ITI TF 2:3.19.6.2, 3.19.6.3, and 3.19.6.4 explains us of ciphers for the ATNA profile.  For the NA 2009 Connectathon, we will follow the ATNA guidelines and allow some extensions.</p> <p><u>HTTP communication</u>: Section 3.19.6.3 requires encryption. In order to support your software, we will allow these two ciphers for HTTP communication: <ol> <li>TLS_RSA_WITH_AES_128_CBC_SHA</li> <li>SSL_RSA_WITH_3DES_EDE_CBC_SHA</li> </ol> <p>This means that you will be responsible to find a partner who supports these ciphers. We will not mandate which ciphers are used by which partners.</p> <H3>Description</H3> <p>The purpose of the ATNA_Authentication_HTTP test is for Secure Nodes or Secure Applications    that communicate using HTTP to use HTTPS and exchange the proper certificates.</p> <p>As a Secure Node or Secure Application at the Connectathon, you need to examine the list of other Secure Nodes and    find a system that you recognize as a test partner for other tests. Once you have found a    suitable test partner that uses HTTPS with mutual authentication, you can run this test.</p><p>Evaluation will require the both applications to show log files or other evidence that    certificates were successfully exchanged and an IHE transaction occurred between the two systems. The transaction is    allowed to cover a subset of an Integration Profile.</p> <H3>Evaluation</H3> <p>Connectathon monitor will examine log files of both applications for evidence of certificate    exchange. Systems should also be able to demonstrate that some transaction was completed (eg RID    Query, XDS Submit Document, XDS Register Document, XDS Query).</p> <p>Systems must support defined cyphersuites. These are found in the IHE ITI Technical Framework; refer to the 'Special Instructions' above.</p> <p>The systems under test need to demonstrate only one type of transaction is operational using    the TLS communication.</p> <p>Monitor will want to see :  <ul><li>TLS Start or equivalent</li> <li>Certificate of both participants</li> <li>Successful TLS handshake</li> <li>The selected CIPHER Suite</li> </ul>  