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 GitHub Bot (Jira)" <ji...@apache.org> on 2023/03/30 15:22:00 UTC

[jira] [Work logged] (KNOX-2895) KnoxShell does not support dynamic truststore type

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

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

                Author: ASF GitHub Bot
            Created on: 30/Mar/23 15:21
            Start Date: 30/Mar/23 15:21
    Worklog Time Spent: 10m 
      Work Description: smolnar82 opened a new pull request, #746:
URL: https://github.com/apache/knox/pull/746

   ## What changes were proposed in this pull request?
   
   Until now, the truststore type was hardcoded to `JKS` in KnoxShell when handling trust stores. With this change, 
   
   ## How was this patch tested?
   
   Added a new unit test case to cover this change and tested manually in a FIPS-enabled cluster where `BCFKS` (Bouncy Castle) truststores were used.
   




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

            Worklog Id:     (was: 853953)
    Remaining Estimate: 0h
            Time Spent: 10m

> KnoxShell does not support dynamic truststore type
> --------------------------------------------------
>
>                 Key: KNOX-2895
>                 URL: https://issues.apache.org/jira/browse/KNOX-2895
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: KnoxShell
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Critical
>             Fix For: 2.1.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, the truststore type in the KnoxShell library is hard coded to "JKS" as opposed to the truststore path and password. We should add the option to be able to configure the truststore type the same way as those properties.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)