[ 
https://issues.apache.org/jira/browse/KNOX-1111?focusedWorklogId=213889&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-213889
 ]

ASF GitHub Bot logged work on KNOX-1111:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 15/Mar/19 17:12
            Start Date: 15/Mar/19 17:12
    Worklog Time Spent: 10m 
      Work Description: risdenk commented on issue #74: KNOX-1111 - 2-way SSL 
Truststore and Keystore Improvements
URL: https://github.com/apache/knox/pull/74#issuecomment-473369994
 
 
   Tests passed locally. Waiting on Travis to merge.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 213889)
    Time Spent: 50m  (was: 40m)

> 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: 50m
>  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)

Reply via email to