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/05/04 11:51:17 UTC

svn commit: r535141 - in /webservices/rampart/trunk/c: INSTALL samples/INSTALL src/util/rampart_timestamp_token.c

Author: kaushalye
Date: Fri May  4 02:51:16 2007
New Revision: 535141

URL: http://svn.apache.org/viewvc?view=rev&rev=535141
Log:
Fixing a bug in timestamp token. Failed if the created time = current time, which was wrong

Modified:
    webservices/rampart/trunk/c/INSTALL
    webservices/rampart/trunk/c/samples/INSTALL
    webservices/rampart/trunk/c/src/util/rampart_timestamp_token.c

Modified: webservices/rampart/trunk/c/INSTALL
URL: http://svn.apache.org/viewvc/webservices/rampart/trunk/c/INSTALL?view=diff&rev=535141&r1=535140&r2=535141
==============================================================================
--- webservices/rampart/trunk/c/INSTALL (original)
+++ webservices/rampart/trunk/c/INSTALL Fri May  4 02:51:16 2007
@@ -102,10 +102,12 @@
 	This will create an axis2 client repository for the samples in the AXIS2C_HOME\clientrepo directory.
 
 3. Set the outflow and inflow secpolicy parameters in axis2.xml of the client repo, according to the scenario that you are running.
+    e.g.
 	<parameter name="OutflowSecurityPolicy">D:\rampart-bin-0.90-win32\samples\secpolicy\scenario1\client-outgoing-secpolicy.xml</parameter> 
 	<parameter name="InflowSecurityPolicy">D:\rampart-bin-0.90-win32\samples\secpolicy\scenario1\client-incoming-secpolicy.xml</parameter> 
 
 4. Set the outflow and inflow secpolicy parameters in services.xml of the sec_echo service in the axis2 server repo.
+    e.g.
 	<parameter name="OutflowSecurityPolicy">D:\rampart-bin-0.90-win32\samples\secpolicy\scenario1\service-outgoing-secpolicy.xml</parameter> 
 	<parameter name="InflowSecurityPolicy">D:\rampart-bin-0.90-win32\samples\secpolicy\scenario1\service-incoming-secpolicy.xml</parameter> 
 

Modified: webservices/rampart/trunk/c/samples/INSTALL
URL: http://svn.apache.org/viewvc/webservices/rampart/trunk/c/samples/INSTALL?view=diff&rev=535141&r1=535140&r2=535141
==============================================================================
--- webservices/rampart/trunk/c/samples/INSTALL (original)
+++ webservices/rampart/trunk/c/samples/INSTALL Fri May  4 02:51:16 2007
@@ -7,6 +7,8 @@
         make install
         use './configure --help' for options
 
+Trying samples
+=============================================
 Please refer the ../INSTALL for more information
 
 

Modified: webservices/rampart/trunk/c/src/util/rampart_timestamp_token.c
URL: http://svn.apache.org/viewvc/webservices/rampart/trunk/c/src/util/rampart_timestamp_token.c?view=diff&rev=535141&r1=535140&r2=535141
==============================================================================
--- webservices/rampart/trunk/c/src/util/rampart_timestamp_token.c (original)
+++ webservices/rampart/trunk/c/src/util/rampart_timestamp_token.c Fri May  4 02:51:16 2007
@@ -138,8 +138,8 @@
     rampart_set_security_processed_result(env, msg_ctx,RAMPART_SPR_TS_CREATED, created_val);
     /*Check whether created is less than current time or not*/
     current_val = rampart_generate_time(env, 0);
-    validity = rampart_compare_date_time(env, created_val, current_val);
-    if (validity == AXIS2_FAILURE)
+    validity = rampart_compare_date_time(env, current_val, created_val);
+    if (validity == AXIS2_SUCCESS)
     {
         AXIS2_LOG_INFO(env->log, "[rampart][ts]Timestamp not valid: Created time is not valid");
         return AXIS2_FAILURE;