<H3>Special Instructions</H3>
 <p>Your ATNA Secure Node or Secure Application may not support profiles which use webservices transactions. 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 2009 Connectathons, we will follow the ATNA guidelines and allow some extensions.</p>
 <p><u>For Web Services communication</u>: Section 3.19.6.4 points to the WS-I Basic Security Profile Version 1.1. For Web Services, we will accept these ciphers:
 <ol>
 <li>TLS_RSA_WITH_3DES_EDE_CBC_SHA</li>
 <li>SSL_RSA_WITH_3DES_EDE_CBC_SHA</li>
 <li>TLS_RSA_WITH_AES_128_CBC_SHA</li>
 <li>SSL_RSA_WITH_AES_128_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>
 <p>Note: the ciphers starting with SSL vs. TLS are identical (i.e. 1. is exactly the same as 2., and 3. is exactly the same as 4.  The reason for this is because the names are for display purposes only; each cipher has a code that goes on the wire (according to the TLS/SSL specs) and there is only one code for, for example, RSA_WITH_3DES_EDE_CBC_SHA, regardless of the TLS or SSL prefix in the display name.</p>
 <H3>Description</H3>
 <p>The purpose of the ATNA_Authentication_Webservices test is for Secure Nodes or Secure Applications
    that communicate using webservices transactions to 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 webservices 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 from the XDS.b, RFD, PIXv3 profiles, among others).</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>
 