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

Rare auth counter behavior is not taken into account by certain tests that use them

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.9.0
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4
    • Sprint:
      Security 2020-10-05, Security 2020-12-28, Security 2021-01-25, Security 2021-02-08, Security 2021-02-22
    • Linked BF Score:
      35

      Description

      If the server receives an auth request that uses saslStart and requires a saslContinue, but never runs saslContinue, then the server will count a received authentication, but not a successful one. There is at least one test that assumes this will never happen, and uses an equal number of received authentication attempts and successful authentication attempts as a metric for correctness. This/these test(s) should take this behavior into account.

      Per Sara Golemon:

      > The right solution may be grabbing the auth stats right after rst.awaitSecondaryNodes(); and verify that speculative, cluster and total auths are all >= ($numberOfNodes - 1). Then trigger all host-connections to re-establish, and get mech stats, then make sure received and successful both went up (and by equal amounts).

        Attachments

          Activity

            People

            Assignee:
            spencer.jackson Spencer Jackson
            Reporter:
            adam.cooper Adam Cooper (Inactive)
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: