Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-14188

Investigate changes in SERVER-54218: Update authentication counter patterns of use

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 4.9.0
    • Component/s: manual, Server
    • Labels:
      None
    • Last comment by Customer:
      true
    • Story Points:
      2
    • Sprint:
      ServerDocs2020: Mar9 - Mar16, ServerDocs2020: Mar16 - Mar23, ServerDocs2020: Mar23 - Mar30, ServerDocs2020: Mar30 - Apr06, ServerDocs2020: Apr6 - Apr13, ServerDocs2020: Apr13 - Apr20, ServerDocs2020: Apr20 - Apr27

      Description

      Description

      Downstream Change Summary

      There is a new counter in serverStatus, security.authentication.saslSupportedMechsReceived, which tracks how many hello requests have included a valid "saslSupportedMechs".

      Description of Linked Ticket

      When we count authentication events using the AuthCounter, we look up a counter in a mechanism map for each event. We can provide handles to counters for a given mechanism to make incrementing the counters more efficient and restrict the failure path more tightly. We can also count use of the saslSupportedMechs field in hello requests.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              naomi.pentrel Naomi Pentrel (Inactive)
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Naomi Pentrel Naomi Pentrel (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                32 weeks, 3 days ago
                Date of 1st Reply: