You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by "Jinsong Lin (JIRA)" <ji...@apache.org> on 2005/07/14 20:20:10 UTC
[jira] Created: (WSS-6) Removed hard-coded BouncyCastle provider from wss4j
Removed hard-coded BouncyCastle provider from wss4j
---------------------------------------------------
Key: WSS-6
URL: http://issues.apache.org/jira/browse/WSS-6
Project: WSS4J
Type: Bug
Environment: all
Reporter: Jinsong Lin
Assigned to: 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 contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Resolved: (WSS-6) Removed hard-coded BouncyCastle provider from wss4j
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/WSS-6?page=all ]
Davanum Srinivas resolved WSS-6:
--------------------------------
Resolution: Fixed
Fixed. just don't include BC jar and there will be no problems.
> Removed hard-coded BouncyCastle provider from wss4j
> ---------------------------------------------------
>
> Key: WSS-6
> URL: http://issues.apache.org/jira/browse/WSS-6
> Project: WSS4J
> 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 contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Resolved: (WSS-6) Removed hard-coded BouncyCastle provider from wss4j
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/WSS-6?page=all ]
Davanum Srinivas resolved WSS-6:
--------------------------------
Resolution: Fixed
Fixed. just don't include BC jar and there will be no problems.
> Removed hard-coded BouncyCastle provider from wss4j
> ---------------------------------------------------
>
> Key: WSS-6
> URL: http://issues.apache.org/jira/browse/WSS-6
> Project: WSS4J
> 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 contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org