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

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

                Author: ASF GitHub Bot
            Created on: 28/May/26 10:23
            Start Date: 28/May/26 10:23
    Worklog Time Spent: 10m 
      Work Description: smolnar82 opened a new pull request, #1242:
URL: https://github.com/apache/knox/pull/1242

   [KNOX-3328](https://issues.apache.org/jira/browse/KNOX-3328) - Add 
Docker-based integration tests for Knox LDAP service
   
   ## What changes were proposed in this pull request?
   
   This PR enhances the integrated Knox LDAP service to support authentication 
(bind operations) and dynamic user/group lookups by proxying requests to an 
external LDAP backend. 
   These changes enable the Knox LDAP service to act as a functional LDAP 
interface for applications that require LDAP-based authentication while 
delegating the actual identity management to a primary directory service.
   
     Key enhancements include:
   
      * Authentication Proxying: Added a bind interceptor to 
`GroupLookupInterceptor` that allows the Knox LDAP server to authenticate users 
against a configured backend (e.g., an external LDAP server or a local 
file-based store).
      * Dynamic User Lookup: Implemented lookup functionality in the 
interceptor to dynamically retrieve user entries from the backend when they are 
not found in the local LDAP partition.
      * Interceptor Reordering: Updated `KnoxLDAPServerManager` to insert the 
`GroupLookupInterceptor` before the standard AuthenticationInterceptor. This 
allows Knox to intercept and process bind requests for non-system users.
      * Backend Interface Update: Extended the LdapBackend interface and its 
implementations (`LdapProxyBackend`, `FileBackend`) with an authenticate method 
to support password verification.
      * Dependency Management: Moved `mina-core` from `test` scope to compile 
scope in `gateway-server` to support the LDAP server's runtime requirements.
      * CI/Test Improvements:
          * Updated the GitHub Actions workflow configuration to enable the 
Knox LDAP service and point it to the demo LDAP backend.
          * Refined the integration tests in 
`test_knox_auth_service_and_LDAP.py` to match the updated service endpoints and 
configurations.
   
   ## How was this patch tested?
   
   I built Knox locally then ran Docker-based integration tests:
   ```
   tests-1  | ============================= test session starts 
==============================
   tests-1  | platform linux 

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

    Worklog Id:     (was: 1022556)
    Time Spent: 3h  (was: 2h 50m)

> Support recursive group resolution in LDAP Proxy Service
> --------------------------------------------------------
>
>                 Key: KNOX-3328
>                 URL: https://issues.apache.org/jira/browse/KNOX-3328
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>    Affects Versions: 3.0.0
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Major
>             Fix For: 3.0.0
>
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> The current Knox LDAP proxy implementation only supports direct group 
> memberships for users. When a client queries for a user's {{memberOf}} 
> attribute, Knox only returns the groups where the user is an explicit member, 
> ignoring any transitive or nested group memberships.
> Additionally, group entries themselves are not enriched with the {{memberOf}} 
> attribute, making it difficult for clients to walk the hierarchy manually.
> This task implements:
> # Recursive group resolution for both search-based and {{memberOf}}-based 
> lookups.
> # Strict cycle detection to prevent infinite loops in misconfigured LDAP 
> environments.
> # Configurable depth limits to prevent performance degradation.
> # Enrichment of group-type entries with the {{memberOf}} attribute, allowing 
> clients to see parent group memberships.



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

Reply via email to