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

Disable UserCacheInvalidator on ldap_runtime_configuration.js

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc17
    • Affects Version/s: None
    • Component/s: None
    • None
    • Server Security
    • Fully Compatible
    • ALL
    • v8.0
    • Security 2024-08-05, Security 2024-08-19
    • 200

      The ldap_runtime_configuration::

      color: Color value is invalid

      runChangeLDAPQueryBindTest

      starts authentication with valid LDAP parameters. These parameters are then changed to invalid ones during the authentication process. It is expected that the authentication will still succeed, even though the parameters were changed to invalid ones, since the changes shouldn't affect an attempt that has already started.

      We are experiencing failures in the test because the user cache is invalidated mid-call from the mongos to the config server. This causes the call to become invalid and a reattempt to be made. This reattempt uses the new, invalid LDAP parameters, which then fail to authenticate.

      We should disable the UserCacheInvalidator periodic job for this test.

            Assignee:
            adrian.gonzalez@mongodb.com Adrian Gonzalez Montemayor
            Reporter:
            adrian.gonzalez@mongodb.com Adrian Gonzalez Montemayor
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: