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
commit 4e9e9903ae7b02cc1db4ad4180a5209ba68144e4 Author: Robert Lazarski <[email protected]> AuthorDate: Wed Nov 18 04:47:12 2026 -1000 RAMPART-463: document that WS-I BSP 1.1 is enforced by default WSS4J applies the Basic Security Profile rules to every received message unless disableBSPEnforcement is set, which is why a UsernameToken whose Password has no Type attribute is rejected although WS-Security makes the attribute optional. The specifications page now lists the profile and the configuration guide explains the switch and its scope. Co-Authored-By: Claude Fable 5.1 <[email protected]> --- src/site/xdoc/rampartconfig-guide.xml | 2 +- src/site/xdoc/specifications.xml | 8 ++++++++ 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/src/site/xdoc/rampartconfig-guide.xml b/src/site/xdoc/rampartconfig-guide.xml index e6bcd93f..8c22e51e 100644 --- a/src/site/xdoc/rampartconfig-guide.xml +++ b/src/site/xdoc/rampartconfig-guide.xml @@ -65,7 +65,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="b"><td>disableBSPEnforcement</td><td>Whether to stop WSS4J enforcing the WS-I Basic Security Profile 1.1 rules on received messages. WSS4J enforces them by default, so Rampart rejects, for example, a UsernameToken whose wsse:Password has no Type attribute (BSP R4201) even though WS-Security itself makes the attribute optional.</td><td>The default is false. Setting it to true turns off every BSP check, not just one, so use it only for peers that cannot be made BSP compliant.</ [...] <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> diff --git a/src/site/xdoc/specifications.xml b/src/site/xdoc/specifications.xml index 70f4559a..a08efdaa 100644 --- a/src/site/xdoc/specifications.xml +++ b/src/site/xdoc/specifications.xml @@ -56,5 +56,13 @@ <li><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512/ws-secureconversation-1.3-os.pdf"> WS Secure Conversation 1.3</a></li> </ul> + <h2>WS-I Basic Security Profile</h2> + <ul> + <li><a href="https://www.ws-i.org/profiles/basicsecurityprofile-1.1.html"> + Basic Security Profile 1.1</a>: WSS4J, which Rampart is built on, enforces the + profile's rules on every received message by default. They are stricter than the + WS-Security specifications they profile. See <code>disableBSPEnforcement</code> in the + <a href="rampartconfig-guide.html">Rampart configuration guide</a>.</li> + </ul> </body> </document> \ No newline at end of file
