Fix failing CSFLE mocked kms tls tests

XMLWordPrintableJSON

    • Type: Build Failure
    • Resolution: Done
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • Dotnet Drivers
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      After enabling tls1.3 support, some CSFLE mocked kms tls tests failed notably on the linux build variants on evergreen. The failing tests were asserting that an authentication error was raised when a client certificate verification failed. However, due to changes in the protocol with tls1.3, a client might consider authentication done even if there was an error with certificate verification and we will not know of an authentication error until we try to read or write to the server. 

              Assignee:
              Adelin Mbida Owona
              Reporter:
              Adelin Mbida Owona
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: