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 in both driver and FLE allow pass through of all LEGAL_TLS_SOCKET_OPTIONS and take the following precedence: 1) top-level Node specific TLS options, including secureContext, 2) MongoDB specified TLS options prefixed with tls*

Testing Requirements

• Integration tests that test all combinations of MongoDB-specific TLS options with Node-specific options
• Pass through of all Node-specific options
• Preference of Node-specific options over MongoDB-specific options
• Note: we do not currently seem to have coverage for the pass through of Node-specific options or for the preference of those over the MongoDB-specific ones

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