Change serialisation of objects for client hash

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Fixed
    • Priority: Major - P3
    • 1.7.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The client hash used to cache a libmongoc client is currently computed by serialising the connection string, along with the options and driverOptions arguments to the MongoDB\Driver\Manager constructor. This causes problems when passing a manager object as part of the autoEncryption options, as the manager can't be serialised.

      To work around this problem, a manager object in that particular option should be exchanged for that particular manager's client hash. This only works for a manager passed as part of the keyVaultClient option of autoEncryption, and should not traverse through all options at this time.

            Assignee:
            Andreas Braun
            Reporter:
            Andreas Braun
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: