[jira] [Work logged] (KNOX-3422) LDAP Proxy shouldn't create user from gateway.ldap.bind.user config

[ASF GitHub Bot (Jira)]

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

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

                Author: ASF GitHub Bot
            Created on: 02/Sep/26 06:10
            Start Date: 02/Sep/26 06:10
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on PR #1371:
URL: https://github.com/apache/knox/pull/1371#issuecomment-5505290164

   ## Test Results
    4 files   4 suites   13s ⏱️
   69 tests 69 ✅ 0 💤 0 ❌
   80 runs  80 ✅ 0 💤 0 ❌
   
   Results for commit 4558ad41.
   
   
[test-results]:data:application/gzip;base64,H4sIAM69l2oC/12MzQ6CMBAGX4X07MFCuxZfxixLSRqBmv6cjO/uQixWL5ud+ZJ5isnNNopro06NiNmlA8YcMDm/MsqOmZe0bdAXuMVM9Gfu7sHmfIgJ3fwjbAg+fEzI61Y05S/BSnx7O1e5nesa+WVxiUEorQ2OSg7QmUGDJZCmv7QKtGwRCS3xBWXE6w0blf/QAAEAAA==
   




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

    Worklog Id:     (was: 1039148)
    Time Spent: 1h 40m  (was: 1.5h)

> LDAP Proxy shouldn't create user from gateway.ldap.bind.user config
> -------------------------------------------------------------------
>
>                 Key: KNOX-3422
>                 URL: https://issues.apache.org/jira/browse/KNOX-3422
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>    Affects Versions: 3.0.0
>            Reporter: David Han
>            Assignee: David Han
>            Priority: Major
>             Fix For: 3.0.0
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> This user configured using the gateway.ldap.bind.user configuration is used 
> to bind against the LDAP Proxy. The gateway server currently creates a user 
> in the local LDAP using this configuration and the aliased password. The 
> downside of this approach is that there is currently no tracking for this 
> user and no way to automatically remove this user if the config changes nor 
> rotate the password. This user is also returned in search queries against the 
> LDAP Proxy.
> I propose creating a new authentication interceptor to manage this user 
> in-memory. This way the user won't be persisted and will automatically be 
> unable to authenticate if the configuration changes.



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