cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alessio Soldano (Updated) (JIRA)" <>
Subject [jira] [Updated] (CXF-4052) Crypto cache issues and the PolicyBasedWSS4JInInterceptor used as a singleton
Date Fri, 10 Feb 2012 16:58:59 GMT


Alessio Soldano updated CXF-4052:

    Fix Version/s: 2.6

Added 2.6 fix version (as it's committed on trunk too)
> Crypto cache issues and the PolicyBasedWSS4JInInterceptor used as a singleton
> -----------------------------------------------------------------------------
>                 Key: CXF-4052
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.4.5, 2.5.2
>         Environment: JBossWS-CXF integration, using Apache CXF 2.4.x
>            Reporter: Alessio Soldano
>            Assignee: Colm O hEigeartaigh
>             Fix For: 2.4.7, 2.5.3, 2.6
>         Attachments: cxf-4052-2.patch, cxf-4052.patch
> When using WS-Policy to setup WS-Security interceptors, the WSSecurityInterceptorProvider
> {code}
> ...
> this.getInInterceptors().add(PolicyBasedWSS4JInInterceptor.INSTANCE);
> this.getInFaultInterceptors().add(PolicyBasedWSS4JInInterceptor.INSTANCE);
> ...
> {code}
> which causes the same instance of PolicyBasedWSS4JInInterceptor to be added to any bus.
> Unfortunately, the PolicyBasedWSS4JInInterceptor ends up extending
which has a Map<String, Crypto> attribute. That is used whenever loading a Crypto instance
and caches instances with keys basically given by the Merlin prop file name the user specified
for the endpoint.
> So, when having multiple deployments referencing properties files with the same name,
the first crypto instance is always used.
> If we want to keep the singleton approach on using the PolicyBasedWSS4JInInterceptor,
we should probably at least use a different mechanism for creating keys so that prop files
from different deployments are kept separate.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message