[
https://issues.apache.org/jira/browse/WSS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712127#comment-15712127
]
Colm O hEigeartaigh commented on WSS-596:
-----------------------------------------
I'll remove the static call in CryptoFactory for 2.2.0. However, I don't want
to remove it for existing releases as it may break some downstream code. As a
workaround, can you just call WSProviderConfig.init(boolean, boolean, boolean)
before the CryptoFactory class is referenced?
> org.apache.wss4j.common.crypto.CryptoFactory add security provider always
> -------------------------------------------------------------------------
>
> Key: WSS-596
> URL: https://issues.apache.org/jira/browse/WSS-596
> Project: WSS4J
> Issue Type: Improvement
> Environment: Websphere Application Server 8.5.5.5 +
> jdk1.7.0_32-ibm_SR8_FP10
> Reporter: Isabel Galan
> Assignee: Colm O hEigeartaigh
> Fix For: 2.2.0
>
>
> I'm using wss4j-ws-security-common to get WS-Security in an application
> deployed at WAS85. I would like not to add providers extra, because interfere
> with some JVMs (such as IBMs).
> WSProviderConfig.class has two methods init() and init(boolean
> addXMLDSigRIInternalProv, boolean addBCProv, boolean addTLProv). The second
> one allows to decide whether add or not providers. That's OK.
> But, I also need to use org.apache.wss4j.common.crypto.CryptoFactory class
> and this class always execute WSProviderConfig.init().
> It would be an improvement to allow if add provider or not when
> CryptoFactory.class is used.
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
