cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r860018 - in /websites/production/cxf/content: cache/docs.pageCache docs/ws-security.html
Date Fri, 26 Apr 2013 16:48:01 GMT
Author: buildbot
Date: Fri Apr 26 16:48:00 2013
New Revision: 860018

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/docs.pageCache
    websites/production/cxf/content/docs/ws-security.html

Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/docs/ws-security.html
==============================================================================
--- websites/production/cxf/content/docs/ws-security.html (original)
+++ websites/production/cxf/content/docs/ws-security.html Fri Apr 26 16:48:00 2013
@@ -333,6 +333,8 @@ CryptoCoverageChecker checker = <span cl
 </pre>
 </div></div>
 
+<p>As of CXF 2.5.11, 2.6.8 and 2.7.5, it is possible to only check that a received
message meets cryptographic requirements via the CryptoCoverageChecker if it is not a fault.
This is useful in the scenario where a client is using the CryptoCoverageChecker interceptor
to verify security requirements from a service response. In this scenario, you may want to
get the original service Fault rather than have the CryptoCoverageChecker throw an exception
if a Fault message from the service isn't secured. To enable this behaviour, then set the
"checkFaults" boolean property on CryptoCoverageChecker to "false".</p>
+
 <h3><a shape="rect" name="WS-Security-CustomProcessors"></a>Custom Processors</h3>
 
 <p>As of CXF 2.0.10 and 2.1.4, you can specify custom WSS4J Processor configurations
on the WSS4JInInterceptor.  To activate this configuration option, one provides a non-WSS4J
defined property, wss4j.processor.map, to the WSS4JInInterceptor as shown in the following
Spring example.  The same configuration can be achieved through the API as well.  The key
value is an XML qualified name of the WS-Security header element to process with the given
processor implementation.  The entry values can be a String representing a class name of the
processor to instantiate, an Object implementing Processor, or null to disable processing
of the given WS-Security header element.</p>



Mime
View raw message