[SERVER-60908] Windows LDAP timeout affects expected behavior in pooled timeout test Created: 21/Oct/21  Updated: 29/Oct/23  Resolved: 25/Oct/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.2.0

Type: Bug Priority: Major - P3
Reporter: Varun Ravichandran Assignee: Varun Ravichandran
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: Windows
Sprint: Security 2021-11-01
Participants:
Linked BF Score: 136

 Description   

BF-22963 appears to be caused by winldap occasionally enforcing the timeout rather than the connection pool. This results in situations where more auth attempts fail than expected by the test, since the ldap_timeout_pooled.js test assumes that the native LDAP libraries are essentially not working and purely tries to test that MongoDB's connection pool is enforcing the timeouts as intended.

In order to ensure that the test is only validating the LDAP connection pool's ability to enforce timeouts, an additional failpoint should be created and set by the test which effectively disables or resets the native LDAP library's timeout to some arbitrarily high value. This should result in a consistent number of expected successes and failures that aligns with what the test currently expects. 



 Comments   
Comment by Githook User [ 25/Oct/21 ]

Author:

{'name': 'Varun Ravichandran', 'email': 'varun.ravichandran@mongodb.com', 'username': 'varunravi98'}

Message: SERVER-60908: Reset native LDAP connection timeouts on timeout tests
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/1918dbde223d887dd0075cb7470b67bca6c4e746

Generated at Thu Feb 08 05:51:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.