[WSS-507] ThreadLocal based Security Provider proxy

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.2
• Component/s: WSS4J Core
• Assignee: Colm O hEigeartaigh
• Reporter: Alessio Soldano
• Created: 25/Jul/14 10:43
• Updated: 04/Oct/14 21:08
• Resolved: 25/Jul/14 16:07

Description

This feature request is about adding a mechanism for making WSS4J (and possibly other projects relying on it) transparently use a Security Provider without globally installing it the JVM. This prevents side effects on other frameworks running within the same JVM and not wanting the BouncyCastle provider currently registered by WSS4J.
The idea is to register a provider acting as a proxy to a different and thread local scoped provider. The proxied provider reference would have to be set and cleaned up by the WSS4J consumers. The reference being thread local ensures different threads don't have access to it. When no proxied provider is set, the installed provider basically serves no algorithm / service.

Issue Links

• is depended upon by: CXF-5905 Allow setting additional Security Provider at Exchange level