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 (JIRA)" <ji...@apache.org> on 2011/02/09 11:34:57 UTC
[jira] Created: (WSS-269) Refactor the Crypto interface
Refactor the Crypto interface
-----------------------------
Key: WSS-269
URL: https://issues.apache.org/jira/browse/WSS-269
Project: WSS4J
Issue Type: Task
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
Fix For: 1.6
The Crypto interface is too closely tied in to the concept of having java KeyStore objects to act as the KeyStore/TrustStore. This refactoring effort should try to abstract this interface, to make it suitable for other use-cases, e.g.:
- Just have an X509Certificate (chain) to verify inbound signatures
- Dispatch an X509Certificate to an XKMS provider for authentication.
--
This message is automatically generated by JIRA.
-
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
[jira] Closed: (WSS-269) Refactor the Crypto interface
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh closed WSS-269.
-----------------------------------
> Refactor the Crypto interface
> -----------------------------
>
> Key: WSS-269
> URL: https://issues.apache.org/jira/browse/WSS-269
> Project: WSS4J
> Issue Type: Task
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Fix For: 1.6
>
>
> The Crypto interface is too closely tied in to the concept of having java KeyStore objects to act as the KeyStore/TrustStore. This refactoring effort should try to abstract this interface, to make it suitable for other use-cases, e.g.:
> - Just have an X509Certificate (chain) to verify inbound signatures
> - Dispatch an X509Certificate to an XKMS provider for authentication.
--
This message is automatically generated by JIRA.
-
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
[jira] Resolved: (WSS-269) Refactor the Crypto interface
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh resolved WSS-269.
-------------------------------------
Resolution: Fixed
> Refactor the Crypto interface
> -----------------------------
>
> Key: WSS-269
> URL: https://issues.apache.org/jira/browse/WSS-269
> Project: WSS4J
> Issue Type: Task
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Fix For: 1.6
>
>
> The Crypto interface is too closely tied in to the concept of having java KeyStore objects to act as the KeyStore/TrustStore. This refactoring effort should try to abstract this interface, to make it suitable for other use-cases, e.g.:
> - Just have an X509Certificate (chain) to verify inbound signatures
> - Dispatch an X509Certificate to an XKMS provider for authentication.
--
This message is automatically generated by JIRA.
-
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