Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
Unknown
Description
UsernameTokenInterceptor does not propagate the ws-security.is-bsp-compliant setting into the WSS4J WSSConfig. We should do that, possibly still defaulting to BSP compliance ON to keep the current behavior if nothing is set.
Attachments
Issue Links
- is related to
-
CXF-3701 CXF 2.4.1 only supports base64 encoding for nonce of a wsse UserToken
- Closed