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

ASF GitHub Bot logged work on HIVE-23958:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 13/Aug/20 00:08
            Start Date: 13/Aug/20 00:08
    Worklog Time Spent: 10m 
      Work Description: risdenk commented on pull request #1342:
URL: https://github.com/apache/hive/pull/1342#issuecomment-673169549


   closed via 
https://github.com/apache/hive/commit/2b3c689baff857c18164a9610f2854583105734a


----------------------------------------------------------------
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:
us...@infra.apache.org


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

    Worklog Id:     (was: 470006)
    Time Spent: 1h  (was: 50m)

> HiveServer2 should support additional keystore/truststores types besides JKS
> ----------------------------------------------------------------------------
>
>                 Key: HIVE-23958
>                 URL: https://issues.apache.org/jira/browse/HIVE-23958
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2
>            Reporter: Kevin Risden
>            Assignee: Kevin Risden
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Currently HiveServer2 (through Jetty and Thrift) only supports JKS (and 
> PCKS12 based on JDK fallback) keystore/truststore types. There are additional 
> keystore/truststore types used for different applications like for FIPS 
> crypto algorithms. HS2 should support the default keystore type specified for 
> the JDK and not always use JKS.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to