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

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

                Author: ASF GitHub Bot
            Created on: 05/Mar/25 23:44
            Start Date: 05/Mar/25 23:44
    Worklog Time Spent: 10m 
      Work Description: lmccay opened a new pull request, #1002:
URL: https://github.com/apache/knox/pull/1002

   ## What changes were proposed in this pull request?
   
   Added Alias support for the truststore password.
   Also moved the creation and load of the truststore to the init method rather 
than the request processing path.
   This required an adjustment in the way that the topology level truststore 
tests were written and the expectations to fail fast at init time which broke 
previous expectations of the request results reflecting truststore issues or 
success.
   
   ## How was this patch tested?
   
   Existing unit tests and new test approaches for previously provided local 
truststore.
   Manual run with separate Knox instance and export cert as the truststore.
   
   




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

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

> Alias Support for the RemoteAuthProvider truststore password
> ------------------------------------------------------------
>
>                 Key: KNOX-3107
>                 URL: https://issues.apache.org/jira/browse/KNOX-3107
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Larry McCay
>            Assignee: Larry McCay
>            Priority: Major
>             Fix For: 2.2.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Need to add Alias support for protecting the topology level config for the 
> RemoteAuthProvider truststore. While it is likely that it will usually 
> leverage the gateway level truststore and not need this for anything but 
> testing and dev environments, some usecases/deployments may want to configure 
> this at the topology level.
> Let's not require the password to be in the topology file.



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

Reply via email to