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

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

                Author: ASF GitHub Bot
            Created on: 11/Nov/26 02:46
            Start Date: 11/Nov/26 02:46
    Worklog Time Spent: 10m 
      Work Description: handavid opened a new pull request, #1504:
URL: https://github.com/apache/knox/pull/1504

   [KNOX-3562](https://issues.apache.org/jira/browse/KNOX-3562) - LDAP Proxy 
accepts non-domain remote base dn
   
   ## What changes were proposed in this pull request?
   
   Loosen the restrictions on the object class of the entry representing the 
remote base dn. This allows configuring a remote base dn other than a domain. 
e.g., cn=accounts,dc=domain,dc=com
   
   ## How was this patch tested?
   
   Added unit test cases.
   
   Manually tested by configuring non-domain remote base dn. This would fail 
before this patch and succeed afterwards.
   ```
       <property>
           <name>gateway.ldap.interceptor.demoldap.remoteBaseDn</name>
           <value>cn=accounts,dc=company,dc=com</value>
           <description>Base DN of the remote LDAP server</description>
       </property>
   ```
   
   ## Integration Tests
   
   no integration tests added
   
   ## UI changes
   
   no UI changes




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

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

> Accept cn for backend search base dn
> ------------------------------------
>
>                 Key: KNOX-3562
>                 URL: https://issues.apache.org/jira/browse/KNOX-3562
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: LDAP
>    Affects Versions: 3.0.0
>            Reporter: David Han
>            Assignee: David Han
>            Priority: Major
>             Fix For: 3.1.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The LDAP Proxy creates base entries for the configured backend DNs. The code 
> is limited to handling dc values only. The LDAP Proxy doesn't really care 
> what the value of the backend base DN is since it's passed on through to the 
> backend. We do need to create the DN in the LDAP Proxy so that the searches 
> for the backend DN are accepted. Loosen the restrictions on DN to accept cn 
> values as well.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to