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

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

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

   [KNOX-3431](https://issues.apache.org/jira/browse/KNOX-3431) - 
UserSearchInterceptor throws exceptions on failed search
   
   ## What changes were proposed in this pull request?
   
   Improve the behavior such that the UserSearchInterceptor will throw 
exceptions when a search request fails rather than swallowing the exception. 
Swallowing exceptions make it difficult to tell if there is a problem 
communicating with the remote LDAP backend.
   
   ## How was this patch tested?
   
   Added unit tests.
   
   ## Integration Tests
   
   Ran existing workflow tests.
   
   ## UI changes
   
   no UI changes




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

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

> LDAP Proxy search should throw exception when any backend fails
> ---------------------------------------------------------------
>
>                 Key: KNOX-3431
>                 URL: https://issues.apache.org/jira/browse/KNOX-3431
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>    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 UserSearchInterceptor currently logs and swallows exceptions when a 
> search request to the backend fails. This has the unfortunate effect of 
> making it very difficult to tell if there were configuration or network 
> errors connecting to the remote backend. Since the exceptions is swallowed, a 
> connection error will look like users have been deleted. It would be better 
> to raise the exception so it's obvious that there is a problem communicating 
> with the remote backend.



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

Reply via email to