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 2016/02/29 12:32:18 UTC

[jira] [Commented] (WSS-571) Truststore Provider

    [ https://issues.apache.org/jira/browse/WSS-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171770#comment-15171770 ] 

Colm O hEigeartaigh commented on WSS-571:
-----------------------------------------

I would prefer if the Crypto interface was not modified, or if it was only modified for WSS4J master, as there are downstream implementations of it that will break otherwise. Could you also make sure that in Merlin it falls back to use the keystore provider to load the truststore, if the truststore provider isn't specified?

Colm.

> Truststore Provider
> -------------------
>
>                 Key: WSS-571
>                 URL: https://issues.apache.org/jira/browse/WSS-571
>             Project: WSS4J
>          Issue Type: New Feature
>            Reporter: Christian Mäder
>            Assignee: Colm O hEigeartaigh
>         Attachments: feature_truststoreprovider.diff
>
>
> This patch adds a truststore provider to Merlin.
> I needed this, because my truststore is software based, whereas my keystore is hardware backed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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