[
https://issues.apache.org/jira/browse/WSS-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved WSS-736.
-------------------------------------
Resolution: Fixed
> WSSConfig.cleanUp() removes security providers registered by other
> deployments of WSS4J
> ---------------------------------------------------------------------------------------
>
> Key: WSS-736
> URL: https://issues.apache.org/jira/browse/WSS-736
> Project: WSS4J
> Issue Type: Improvement
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Priority: Major
> Fix For: 4.0.3
>
>
> When WSS4J is packaged inside more than one web application in the same JVM,
> for example two WARs on one Tomcat, every copy registers JVM-wide JCA
> providers under the same names: {{{}STRTransform{}}},
> {{{}AttachmentContentSignatureTransform{}}},
> {{AttachmentCompleteSignatureTransform}} and {{ApacheXMLDSig}} (plus
> {{{}BC{}}}/{{{}TLSP{}}} if requested).
> {{WSSConfig.cleanUp()}} and {{WSProviderConfig.cleanUp()}} removed these
> providers by name. So when one application was undeployed, for example
> through {{{}WssServletContextListener{}}}, it also removed the providers that
> another running application had registered. That application then failed, for
> example with {{NoSuchAlgorithmException}} for the attachment or STR
> transforms. {{cleanUp()}} also removed a {{BC}} provider that was registered
> before WSS4J was initialised.
> *Fix:* WSS4J now records the provider instances it actually registers, and
> {{cleanUp()}} removes a provider only if that instance is still the one
> registered under the name. {{WSSConfig.init()}} also logs a warning when it
> replaces a transform provider that was registered by a different class
> loader, because in that case the other application may fail with a
> class-loader mismatch, as reported in this issue.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]