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

Ability to reuse a single TCP connection from mongod to the LDAP server

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • v4.0, v3.6
    • Security 2018-12-17, Security 2018-12-31, Security 2019-01-14, Security 2019-01-28

    Description

      When enabling LDAP in the typical setting, mongod process is using the three separate TCP connections to the LDAP server(s) for every db.auth() command:
      1. One (or more) connections for the sections in the security.ldap.userToDNMapping option with the ldapQuery predicates
      2. A single connection to authenticate the user by using the bind operation
      3. A single connection to obtain the list of groups for authorization.

      I am wondering if we could create a single TCP connection during the step 1 or 2 and reuse it for the next steps without reestablishing connection every time for the particular thread (==session) in the server?

      Attachments

        Issue Links

          is documented by

          Task - A task that needs to be done. DOCS-12401 Docs for SERVER-34260: Ability to reuse a single TCP connection from mongod to the LDAP server

          • Major - P3 - Major loss of function.
          • Closed
          is duplicated by

          Task - A task that needs to be done. SERVER-38885 Log LDAP thread safety warning only once.

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          New Feature - A new feature of the product, which has yet to be developed. SERVER-37193 Implement connection pooling for the LDAP servers

          • Major - P3 - Major loss of function.
          • Closed

          Question - SERVER-33852 libldap is not threadsafe with NSS

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Task - A task that needs to be done. DOCS-12337 Docs for SERVER-33852: libldap is not threadsafe with NSS

          • Major - P3 - Major loss of function.
          • In Progress

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-35010 LDAP failover/failback selection is suboptimal

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              jonathan.reams@mongodb.com Jonathan Reams
              andrey.brindeyev@mongodb.com Andrey Brindeyev
              Votes:
              3 Vote for this issue
              Watchers:
              142 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: