You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2014/07/25 18:08:38 UTC
[jira] [Resolved] (WSS-507) ThreadLocal based Security Provider
proxy
[ https://issues.apache.org/jira/browse/WSS-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh resolved WSS-507.
-------------------------------------
Resolution: Fixed
> ThreadLocal based Security Provider proxy
> -----------------------------------------
>
> Key: WSS-507
> URL: https://issues.apache.org/jira/browse/WSS-507
> Project: WSS4J
> Issue Type: New Feature
> Components: WSS4J Core
> Reporter: Alessio Soldano
> Assignee: Colm O hEigeartaigh
> Fix For: 2.0.2
>
> Attachments: proposal.diff
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org