The ldap_runtime_configuration::

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.