[
https://issues.apache.org/jira/browse/CXF-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessio Soldano resolved CXF-5905.
----------------------------------
Resolution: Fixed
> Allow setting additional Security Provider at Exchange level
> ------------------------------------------------------------
>
> Key: CXF-5905
> URL: https://issues.apache.org/jira/browse/CXF-5905
> Project: CXF
> Issue Type: New Feature
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: 3.0.2, 3.1.0
>
> Attachments: initial-patch.diff
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
