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 2019/03/15 17:29:00 UTC
[jira] [Commented] (KNOX-1111) 2-way SSL Truststore and Keystore
Improvements
[ https://issues.apache.org/jira/browse/KNOX-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793795#comment-16793795 ]
ASF subversion and git services commented on KNOX-1111:
-------------------------------------------------------
Commit d96128dfa3d8c8a656a94d97719fb28737fae925 in knox's branch refs/heads/master from Robert Levas
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=d96128d ]
KNOX-1111 - 2-way SSL Truststore and Keystore Improvements (#74)
> 2-way SSL Truststore and Keystore Improvements
> ----------------------------------------------
>
> Key: KNOX-1111
> URL: https://issues.apache.org/jira/browse/KNOX-1111
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Reporter: Larry McCay
> Assignee: Robert Levas
> Priority: Major
> Fix For: 1.3.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently, the DefaultHttpClientFactory is setting the 2-way SSL for dispatches truststore as gateway.jks. This should be driven by configuration and probably default to cacerts rather than gateway.jks.
> The client cert alias inside the keystore should be configurable as well so that we can possibly have different certs representing different topologies.
> In addition, the keystore to host the client certs should be configurable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)