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 ka...@apache.org on 2007/09/19 06:26:53 UTC
svn commit: r577144 - in /webservices/rampart/trunk/c: INSTALL NEWS README
samples/secpolicy/README.txt
Author: kaushalye
Date: Tue Sep 18 21:26:51 2007
New Revision: 577144
URL: http://svn.apache.org/viewvc?rev=577144&view=rev
Log:
Updating READMEs INSTALLs
Modified:
webservices/rampart/trunk/c/INSTALL
webservices/rampart/trunk/c/NEWS
webservices/rampart/trunk/c/README
webservices/rampart/trunk/c/samples/secpolicy/README.txt
Modified: webservices/rampart/trunk/c/INSTALL
URL: http://svn.apache.org/viewvc/webservices/rampart/trunk/c/INSTALL?rev=577144&r1=577143&r2=577144&view=diff
==============================================================================
--- webservices/rampart/trunk/c/INSTALL (original)
+++ webservices/rampart/trunk/c/INSTALL Tue Sep 18 21:26:51 2007
@@ -18,9 +18,10 @@
make
make install
-If you need to try samples, you need to build them.
- -Go to samples and run the script build.sh
- -Then go to samples/secpolicy and try a scenario
+If you need to try samples,first you need to build them.
+Go to samples and run the script build.sh.
+ %sh build.sh
+Then go to samples/secpolicy and try a scenario
%sh test_scen.sh scenarioX server-port
Getting Rampart/C binary distribution working on Linux
@@ -78,7 +79,7 @@
<phase name="Security"/>
</phaseOrder>
-To specify policies in the client side, please drop your policy.xml to the same directory as in axis2.xml
+To specify policies in the client side, please drop your policy.xml to the same directory where the axis2.xml is in.
To specify policies in the server side, please add policy assertions to the services.xml.
Please find such sample policy files under samples/secpolicy/scenarioX.
Note that you must replace both the client and service policies for a particular scenario.
@@ -89,7 +90,7 @@
Run a scenario that you'd like to try using the script test_scen.sh
Syntax: test_scen.sh scenario server_port
E.g. %sh test_scen.sh scenario3 9090
-Note: You may use a TCP Monitor to see the wire content. In that case replace the server_port with the lietening port
+Note: You may use a TCP Monitor to see the wire content. In that case replace the server_port with the lietening port.
Try samples on Win32
===============================
Modified: webservices/rampart/trunk/c/NEWS
URL: http://svn.apache.org/viewvc/webservices/rampart/trunk/c/NEWS?rev=577144&r1=577143&r2=577144&view=diff
==============================================================================
--- webservices/rampart/trunk/c/NEWS (original)
+++ webservices/rampart/trunk/c/NEWS Tue Sep 18 21:26:51 2007
@@ -23,4 +23,3 @@
We welcome your early feedback on this implementation.
Thanks for your interest in Rampart/C
-
Modified: webservices/rampart/trunk/c/README
URL: http://svn.apache.org/viewvc/webservices/rampart/trunk/c/README?rev=577144&r1=577143&r2=577144&view=diff
==============================================================================
--- webservices/rampart/trunk/c/README (original)
+++ webservices/rampart/trunk/c/README Tue Sep 18 21:26:51 2007
@@ -5,11 +5,9 @@
-----------
Apache Rampart/C is the security module of the Apache Axis2/C. Rampart/C
- is an effort to implement Axis2 Rampart module in C.
-
- Please have a look at
- http://ws.apache.org/axis2/modules/rampart/1_0/security-module.html
- for an overview on Axis2 rampart.
+ is an effort to implement WS-Security sepcification in C language.
+ In addition Apache Rampart/C configurations are based on security policy assertions as per WS-Security Policy specificatoin.
+ Please have a look at http://ws.apache.org/rampart/c/ for more information.
As a project of the Apache Software Foundation, the
developers aim to collaboratively develop and maintain a robust,
@@ -45,8 +43,8 @@
at http://issues.apache.org/jira/browse/RAMPARTC
o If you want to participate in actively developing Apache Rampart/C please
- subscribe to the `axis-c-dev@ws.apache.org' mailing list as described at
- http://ws.apache.org/axis2/c/mail-lists.html
+ subscribe to the `rampart-c-dev@ws.apache.org' mailing list as described at
+ http://ws.apache.org/rampart/c/lists_issues.html
Acknowledgments
----------------
Modified: webservices/rampart/trunk/c/samples/secpolicy/README.txt
URL: http://svn.apache.org/viewvc/webservices/rampart/trunk/c/samples/secpolicy/README.txt?rev=577144&r1=577143&r2=577144&view=diff
==============================================================================
--- webservices/rampart/trunk/c/samples/secpolicy/README.txt (original)
+++ webservices/rampart/trunk/c/samples/secpolicy/README.txt Tue Sep 18 21:26:51 2007
@@ -31,18 +31,16 @@
* I am in a HURRY and I need to try a scenario
--------------------------------------------
If you are in a real hurry and need to try a scenario please use "test_scen.sh".
-
Usage : %sh test_scen.sh scenarioX server-port
E.g. %sh test_scen.sh scenario3 8080
* I need to try all the scenarios
-------------------------------
In this case please use the script run_all.sh.
-
Usage: %sh run_all.sh server-port
E.g. %sh run_all.sh 8080
-* I need to see the messages exchanged
+* I need to see messages exchanged
--------------------------------------
You may use the TCP Monitor utility: http://ws.apache.org/commons/tcpmon/
@@ -51,6 +49,22 @@
* I cannot run samples and log says keys cannot be loaded
---------------------------------------------------------
-Check you rpolicy files. Make sure that you have correct paths specified for
+Check your policy files. Make sure that you have correct paths specified for
key/certificate files.
+
+* My client sends a secured SOAP request. But the server throws me SOAP faults.
+------------------------------------------------------------------------------
+Well. You are on it. Check whether the server's policy configurations are
+satisfied by the client's policies. There is a <Reason> element carrying the
+information you need in the SOAP fault. Misconfigurations in the server also can be resulted
+in a SOAP fault.
+
+*Hmm... I'm still in a trouble. Can I contact you guys?
+-------------------------------------------------------
+Indeed you can. Please check here.
+http://ws.apache.org/rampart/c/lists_issues.html
+Err... if you can attach log files under AXIS2C_HOME/logs, a trace of SOAP
+message, plus anything that you think relavent, that'll help the troubleshooting process.
+
+