[DOCS-16184] [Server] Investigate changes in SERVER-71606: Pass const int* instead of timeval* for LDAP_OPT_TIMELIMIT Created: 05/Jun/23  Updated: 13/Nov/23  Resolved: 11/Jul/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 6.3.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: David Hou
Resolution: Done Votes: 0
Labels: quick-win, server-docs-bug-bash
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-71606 Pass const int* instead of timeval* f... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
DOCS-16255 Backport to 6.3 Sub-task Closed David Hou  
Participants:
Days since reply: 30 weeks, 1 day ago

 Description   
Original Downstream Change Summary

The `security.ldap.timeoutMS` option was changed to accept 32-bit integers (int) instead of 64-bit integers (long). This was done after discovering that the underlying system library (OpenLDAP) only accepts 32-bit integers for its timeout. The docs should be updated to state that this option takes int rather than long.

Description of Linked Ticket

When LDAP_OPT_TIMELIMIT is set, OpenLDAP casts the value provided to a const int* (see here). Currently, we pass in the address to timeout, which is of type timeval

We should pass the correct type here to avoid unexpected behavior due to casting.



 Comments   
Comment by David Hou [ 11/Jul/23 ]

https://github.com/10gen/docs-mongodb-internal/pull/3572

Generated at Thu Feb 08 08:14:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.