Project

General

Profile

Bug #17267

exception in ldap search are not correctly caught

Added by Nicolas CHARLES 5 months ago. Updated 2 months ago.

Status:
Released
Priority:
N/A
Category:
Security
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

Description

When there's a timeout, it's not correctly catched, and bubble all the way up

LDAPException(resultCode=85 (timeout), numEntries=25, numReferences=0, diagnosticMessage='A client-side timeout was encountered while waiting 300000ms for a response to search request with message ID 81, base DN
 'ou=Inventories,cn=rudder-configuration', scope SUB, and filter '(|(nodeId=d8a7c836-131d-44ea-acac-8c1b1002c6ff)(nodeId=da08e6ce-f00a-4a55-bcf8-f2cf3a3b33ca)(nodeId=70f1eb83-0c6e-4dd3-8064-05ca00d00459)(nodeId=
99715ed9-c5cb-40ca-b8b3-081d9472ad27)(nodeId=683ae90f-8d5d-43d3-9904-054d5c2777dc)(nodeId=aee66517-b1af-4045-89f0-c75200ee2f51)(nodeId=dcd7dab7-95aa-4c5d-bb2a-d60e7c5cd152)(nodeId=6fe1f84f-2716-4286-b0c2-282c75c
d7ca4)(nodeId=66d8032e-c624-4438-9b7a-4927bd939279)(nodeId=d6844127-93e2-4799-be6c-9df596511eb8)(nodeId=1ee3151e-68a3-4634-bead-d5beb538d3f1)(nodeId=fe455170-e1d1-42cc-a683-59567f85f8ce)(nodeId=1c6fc675-250a-47e
1-98cd-6a42b21fc298)(nodeId=53d42482-59b2-4b9d-a341-03068b02157f)(nodeId=80eb7321-0472-4f30-b03f-f37c96930816)(nodeId=8a2ab60f-80fc-410b-8b2e-0798b2a7cbd2)(nodeId=22afc674-916b-4366-8211-835b59b3efd7)(nodeId=ec5
eab0a-47fe-4c03-b389-b42721d99e84)(nodeId=9e93ef2d-5b56-4e3f-8b1d-d32c28672a5f)(nodeId=59ee6666-8f30-4284-a31d-980e73178504)(nodeId=737cd523-41b0-4dd2-91ee-1c32e5743334)(nodeId=1ffb6db6-0576-4898-8c7e-c643800767
21)(nodeId=d41399e0-168b-4d27-a244-777f9b6ad318)(nodeId=47c73aa0-7c0c-4556-96a3-d030525190e7)(nodeId=d1464cb1-6506-460a-bfda-fec13727eb81))' from server localhost:389.', ldapSDKVersion=4.0.7, revision=28484')
        at com.unboundid.ldap.sdk.SearchRequest.process(SearchRequest.java:1206)
        at com.unboundid.ldap.sdk.LDAPConnection.search(LDAPConnection.java:3757)
        at com.normation.ldap.sdk.RoLDAPConnection.search(LDAPConnection.scala:302)
        at com.normation.ldap.sdk.ReadOnlyEntryLDAPConnection.search(LDAPConnection.scala:82)
        at com.normation.ldap.sdk.ReadOnlyEntryLDAPConnection.search$(LDAPConnection.scala:81)
        at com.normation.ldap.sdk.RoLDAPConnection.search(LDAPConnection.scala:283)
        at com.normation.ldap.sdk.ReadOnlyEntryLDAPConnection.searchSub(LDAPConnection.scala:158)

it should be nicely caught, maybe in the search itself

#1

Updated by Nicolas CHARLES 5 months ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
#2

Updated by Nicolas CHARLES 5 months ago

  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/2943
#3

Updated by Nicolas CHARLES 5 months ago

  • Status changed from In progress to Pending release
#5

Updated by Vincent MEMBRÉ 2 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.18 and 6.1.2 which were released today.

Also available in: Atom PDF