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

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

                Author: ASF GitHub Bot
            Created on: 21/Apr/26 13:44
            Start Date: 21/Apr/26 13:44
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on PR #1207:
URL: https://github.com/apache/knox/pull/1207#issuecomment-4289015032

   ## Test Results
   21 tests   21 ✅  1s ⏱️
    1 suites   0 💤
    1 files     0 ❌
   
   Results for commit 59ad7d39.
   
   
[test-results]:data:application/gzip;base64,H4sIACl/52kC/12Nyw6CMBBFf4V07aJIS8WfMX3MJBOBmj5Wxn+3ICngbs65yZk3QxohsnvTXhoWM6UKLgedyM8bliEt07XCI2Zr/8yTXsXwKlDTeBIQgg+bCXmuxeU+BX9i7618yK18rFk/TZQKMDlop1w3gEUlEDiKTqKSwhihbmi5ceDavrz6fAEdxk64/wAAAA==
   




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

    Worklog Id:     (was: 1016688)
    Time Spent: 20m  (was: 10m)

> KnoxLdapContextFactory to lookup system password on gateway-level credential 
> store
> ----------------------------------------------------------------------------------
>
>                 Key: KNOX-3302
>                 URL: https://issues.apache.org/jira/browse/KNOX-3302
>             Project: Apache Knox
>          Issue Type: Task
>          Components: Server
>    Affects Versions: 2.1.0
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Major
>             Fix For: 3.0.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> As of today, the KnoxLdapContextFactory tries to lookup a system password in 
> the given topology's credential store (e.g. sandbox-credentials.jceks), and 
> doesn't fallback to the gateway-level credential store if nothing is there.
> In real-life deployments, topologies usually share the same LDAP instance, 
> thus, configuring the system password on the gateway-level is enough and 
> should be queried from there.



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

Reply via email to