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

setParameter ldapForceMultiThreadMode is not respected

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • 7.0.6, 6.0.14
    • 6.0.6
    • None
    • None
    • Server Security
    • ALL
    • v7.0, v6.0
    • Hide

      1) Spawn a mongod on RHEL 8, enabling LDAP using libldap.so, and enabling ldapForceMultiThreadMode and ldapUseConnectionPool.
      2) Authenticate to the mongod using PLAIN
      3) Check that the numbers returned by db.serverStatus().ldapConnPool are greater than zero

      Show
      1) Spawn a mongod on RHEL 8, enabling LDAP using libldap.so, and enabling ldapForceMultiThreadMode and ldapUseConnectionPool. 2) Authenticate to the mongod using PLAIN 3) Check that the numbers returned by db.serverStatus().ldapConnPool are greater than zero

    Description

      Prior to SERVER-56617, LDAPConnectionFactory::create would create a pooled connection if isNativeImplThreadSafe is true. This would be true if OpenLDAPConnection::isThreadSafe(). This would be true if ldapForceMultiThreadMode had been enabled.

      Now LDAPConnectionFactory::create creates a pooled connection if isNativeImplPoolingSafe() is true. isNativeImplPoolingSafe() is true if the new library traits system says the underlying LDAP library is poolingSafe. It does not consider if ldapForceMultiThreadMode is enabled.

      Attachments

        Activity

          People

            backlog-server-security Backlog - Security Team
            spencer.jackson@mongodb.com Spencer Jackson
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: