[SERVER-79555] Test LDAP runtime configuration changes during long-running LDAP connections Created: 31/Jul/23 Updated: 29/Oct/23 Resolved: 21/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | 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 | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Security 2023-08-07, Security 2023-08-21, Security 2023-09-04 |
| Participants: |
| Description |
|
Today, the LDAPRunner is responsible for storing the runtime-settable LDAP parameters. There is very limited testing to ensure that the runtime-settable options properly take effect on LDAP connections in a defined manner. Adding these tests will increase confidence that runtime LDAP configuration updates do not cause server crashes or undefined behavior. The connection pool is also not informed when the set of LDAP hosts is changed at runtime, causing it to continue maintaining a pool of connections to the old hosts. |