Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-77995

Log connection ID for pooled LDAP connections

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Server Security
    • Security 2023-09-04

      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.

            Assignee:
            backlog-server-security [DO NOT USE] Backlog - Security Team
            Reporter:
            varun.ravichandran@mongodb.com Varun Ravichandran
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: