You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wss4j-dev@ws.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2009/01/06 16:18:44 UTC
[jira] Updated: (WSS-84) Make the use of the VM-wide keystore
(lib/security/cacerts) optional
[ https://issues.apache.org/jira/browse/WSS-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh updated WSS-84:
-----------------------------------
Fix Version/s: (was: 1.5.5)
Leaving this for a future refactoring of how we handle keystores and truststores.
> Make the use of the VM-wide keystore (lib/security/cacerts) optional
> --------------------------------------------------------------------
>
> Key: WSS-84
> URL: https://issues.apache.org/jira/browse/WSS-84
> Project: WSS4J
> Issue Type: Improvement
> Affects Versions: 1.5.4
> Reporter: Christof Soehngen
> Priority: Minor
>
> As of WSS4J 1.5.3, each Merlin-Crypto loads the cacerts as an additional keystore.
> When searching the keystore specified in the properties, the cacerts are taken into account, too.
> Although this behaviour may be useful/desired in many cases, there are cases where the standalone keystore is sufficient.
> It would be an improvement of speed and simplicity if loading of the cacerts keystore could be disabled in the properties that load the crypto.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org