You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by su...@apache.org on 2008/06/10 10:32:21 UTC
svn commit: r666007 - /webservices/rampart/trunk/c/samples/secpolicy/README
Author: supun
Date: Tue Jun 10 01:32:21 2008
New Revision: 666007
URL: http://svn.apache.org/viewvc?rev=666007&view=rev
Log:
Updated the README file for sample scenarios. RAMPARTC-111
Modified:
webservices/rampart/trunk/c/samples/secpolicy/README
Modified: webservices/rampart/trunk/c/samples/secpolicy/README
URL: http://svn.apache.org/viewvc/webservices/rampart/trunk/c/samples/secpolicy/README?rev=666007&r1=666006&r2=666007&view=diff
==============================================================================
--- webservices/rampart/trunk/c/samples/secpolicy/README (original)
+++ webservices/rampart/trunk/c/samples/secpolicy/README Tue Jun 10 01:32:21 2008
@@ -58,7 +58,15 @@
19. Symmetric binding with secure conversation token.
Using different tokens for encryption and signature.
The protection token is Sign->Encrypt. Signature is Encrypted.
-20. SAML Scenario. Cannot be run with test_scen.sh. Please use saml.sh script
+20. SAML Scenario. Get a SAML token from samlsts and give the saml token to sec_echo service to access the service. Cannot be run with test_scen.sh. Please use saml.sh script
+
+21. Asymetric binding encryption with PKCS12 as the key store.
+
+22. Asymetric binding signature with PKCS12 as the key store.
+
+23. Symmetric binding signature and encryption with PKCS12 key store.
+
+24. SAML as a protection token for signing and encrypting a message.
FAQ:
---