summaryrefslogtreecommitdiff
path: root/TAO/orbsvcs/tests/Security/mixed_security_test/README
diff options
context:
space:
mode:
Diffstat (limited to 'TAO/orbsvcs/tests/Security/mixed_security_test/README')
-rw-r--r--TAO/orbsvcs/tests/Security/mixed_security_test/README10
1 files changed, 4 insertions, 6 deletions
diff --git a/TAO/orbsvcs/tests/Security/mixed_security_test/README b/TAO/orbsvcs/tests/Security/mixed_security_test/README
index 422bd9a09d8..67c22d3b92a 100644
--- a/TAO/orbsvcs/tests/Security/mixed_security_test/README
+++ b/TAO/orbsvcs/tests/Security/mixed_security_test/README
@@ -1,6 +1,4 @@
-#
-# $Id$
-#
+$Id$
-----------------------------
cases:
@@ -13,13 +11,13 @@ cases:
This test verifies that the ORB's secure invocation mechanism is
functioning properly. It expands on what the Secure_Invocation does
-by activating an object with two separate ORBs and POAs. One of the POAs
+by activating an object with two separate ORBs and POAs. One of the POAs
has a SecQoPNoProtection policy assigned and thus should permit also
invocations over non-secure transport.
The test verifies that a secure client can make invocations, using both
-the "secure" and the "non-secure" IOR from the server. Note that for
-the server to support the non-secure invocations it must have -SSLNoProtection
+the "secure" and the "non-secure" IOR from the server. Note that for
+the server to support the non-secure invocations it must have -SSLNoProtection
in its sevice configuration file.
The test verifies that a non-secure client can only make invocations through