Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-343

Cache SCRAM ClientKey

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: In Progress
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 3.6 Desired
    • Component/s: None
    • Labels:
      None
    • # Replies:
      1
    • Last comment by Customer:
      false
    • SERVER fixVersion:
      3.6

      Description

      The shell is going to cache and reuse ClientKey in 3.6. We should do the same in drivers. From SERVER-26952 ticket :

      SCRAM, by design, consumes a great deal of CPU resources while performing authentication. This can be a problem while populating connection pools, where many clients are authenticating at once. Fortunately, most of the expensive computations of SCRAM can be reused across multiple authentication requests. RFC5802 makes provisions for this:

      Note that a client implementation MAY cache ClientKey&ServerKey (or just SaltedPassword) for later reauthentication to the same service, as it is likely that the server is going to advertise the same salt value upon reauthentication. This might be useful for mobile clients where CPU usage is a concern.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                behackett Bernie Hackett
                Participants:
                Last commenter:
                Ian Whalen
              • Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Days since reply:
                  1 year, 19 weeks, 4 days ago
                  Date of 1st Reply: