You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@knox.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/04/04 20:17:00 UTC

[jira] [Commented] (KNOX-1238) Fix Custom Truststore Settings for Gateway

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

ASF subversion and git services commented on KNOX-1238:
-------------------------------------------------------

Commit f8cad74ca71768243aadda69bb6cb54067e06656 in knox's branch refs/heads/master from [~lmccay]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=f8cad74 ]

KNOX-1238 - Fix Custom Truststore Settings for Gateway

> Fix Custom Truststore Settings for Gateway
> ------------------------------------------
>
>                 Key: KNOX-1238
>                 URL: https://issues.apache.org/jira/browse/KNOX-1238
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>            Reporter: Larry McCay
>            Assignee: Larry McCay
>            Priority: Major
>             Fix For: 1.1.0
>
>
> After some hair pulling, I realized that the truststore configuration and sslContextFactory creation in JettySSLService is not working properly. It is setting the gateway's identity store as the truststore whether there is a custom truststore configured or not.
> This patch fixes that issue and allows for a separate truststore.
> In the meantime, there is a workaround of adding trusted certs to the gateway.jks keystore or to cacerts for the gateway instance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)