Investigate changes in NODE-7032: Align TLS option handling in the driver

XMLWordPrintableJSON

    • Type: Investigation
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      Use Case

      As a developer
      I want consistent handling of TLS options
      So that I have a clear understanding of the options and which take precedence.

      User Experience

      • Users have a clear understanding of the driver and FLE behaviour when providing TLS options.

      Dependencies

      • Compass/mongosh

      Risks/Unknowns

      • None

      Acceptance Criteria

      Implementation Requirements

      • Ensure that TLS options take the following precedence: 1) secureContext, 2) top-level Node specific TLS options outside secureContext, 3) MongoDB specified TLS options prefixed with tls*

      Testing Requirements

      • Integration tests that test all combinations of the 3 types of options.

      Documentation Requirements

      • API docs stating the order of preference for the options.
      • MongoDB manual docs stating the order of preference for the options.

      Follow Up Requirements

      • None

            Assignee:
            Unassigned
            Reporter:
            TPM Jira Automations Bot
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: