[SERVER-77995] Log connection ID for pooled LDAP connections Created: 12/Jun/23 Updated: 14/Sep/23 |
|
| Status: | Blocked |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Varun Ravichandran | Assignee: | Backlog - Security Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Security
|
||||||||
| Sprint: | Security 2023-09-04 | ||||||||
| Participants: | |||||||||
| Description |
|
Today, connections in the LDAP connection pool do not have any unique IDs. As a result, it is difficult to track per-connection state in the logs (e.g., which connection was refreshed, checked out, used for various operations, ran into an error, etc.). Adding an ID will allow each of these logs to be separable by ID to better trace the cause for failures. |