This is an automated email from the ASF dual-hosted git repository.
robertlazarski pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-rampart.git
The following commit(s) were added to refs/heads/master by this push:
new 3f457fe7 RAMPART-432 Add disableBSPEnforcement to RampartConfig docs
3f457fe7 is described below
commit 3f457fe7408cbb7803506e6c3329b915000e1124
Author: Robert Lazarski <robertlazar...@gmail.com>
AuthorDate: Wed Oct 30 05:35:41 2024 -1000
RAMPART-432 Add disableBSPEnforcement to RampartConfig docs
---
src/site/xdoc/rampartconfig-guide.xml | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/site/xdoc/rampartconfig-guide.xml
b/src/site/xdoc/rampartconfig-guide.xml
index e593b8dd..d313ce9c 100644
--- a/src/site/xdoc/rampartconfig-guide.xml
+++ b/src/site/xdoc/rampartconfig-guide.xml
@@ -55,6 +55,7 @@
....crypto element ......
</decryptionCrypto></pre></td></tr>
<tr class="b"><td>timestampTTL</td><td>Time to live of Timestamp</td><td>The
default timestamp time to live is 300 seconds</td></tr>
+ <tr class="b"><td>disableBSPEnforcement.</td><td>WSS4J param to set on class
RequestData</td><td>The default is false</td></tr>
<tr class="a"><td>timestampMaxSkew</td><td>The maximum tolerence limit for
timeskew of the timestamp</td><td>Rampart allows timestamps created slightly
ahead of the reciever's time.<br/> This parameter allows to specify the
tolerence limit</td></tr>
<tr class="b"><td>timestampPrecisionInMilliseconds</td><td> Whether the
timestamps precision should be milliseconds </td><td>When this value is set
false, generated timestamps doesn't contain milliseconds </td></tr>
<tr class="a"><td>optimizeParts</td><td></td><td></td></tr>
