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 (Closed) (JIRA)" <ji...@apache.org> on 2011/10/03 11:04:42 UTC

[jira] [Closed] (WSS-6) Removed hard-coded BouncyCastle provider from wss4j

     [ https://issues.apache.org/jira/browse/WSS-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh closed WSS-6.
---------------------------------

    
> Removed hard-coded BouncyCastle provider from wss4j
> ---------------------------------------------------
>
>                 Key: WSS-6
>                 URL: https://issues.apache.org/jira/browse/WSS-6
>             Project: WSS4J
>          Issue Type: Bug
>         Environment: all
>            Reporter: Jinsong Lin
>            Assignee: Davanum Srinivas
>
> WSS4J has various place to hard code BouncyCastle provider,  such as WSSecurityEngine.java, WSSecurityUtil.java. This causes problem for users who have their own security providers and don't want to use BouncyCastle. Also since xmlsec already provides a mechansim to configure and load security providers, WSS4J need not to hard code these security providers. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org