[CXF-5905] Allow setting additional Security Provider at Exchange level

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.2, 3.1
• Estimated Complexity: Unknown
• Assignee: Alessio Soldano
• Reporter: Alessio Soldano
• Created: 25/Jul/14 10:44
• Updated: 16/Feb/15 16:09
• Resolved: 29/Jul/14 07:12

Description

This is a follow-up from the CXF dev list thread at http://cxf.547215.n5.nabble.com/On-BouncyCastle-installed-as-a-global-security-provider-td5746785.html and is meant to work with the WSS4J changes at https://issues.apache.org/jira/browse/WSS-507 .
CXF could allow setting a custom (BouncyCastle) security provider in the message exchange; if provided, that would be set into WSS4J ThreadLocalSecurityProvider (when installed) just before running sensible interceptors, and cleaned up just afterwards.
Attached is an initial patch; I'm going to figure out the other WS-Security interceptors that need to be modified if this approach is fine.

Issue Links

• depends upon: WSS-507 ThreadLocal based Security Provider proxy