In the shell, we need to expose the --tlsDisabledProtocols arguments to allow the user to specify additional TLS options.

The driver currently does not support this options. Node.js, however, does, either by passing this information directly as options of tls.connect() or by explicitly creating a SecureContext and passing it there.

Given that the TLS connection is done in the driver, we should be able to pass these options to the driver, along with the other options listed as "legal" here: https://github.com/mongodb/node-mongodb-native/blob/89b77edbdd89d40c8a908a3ae4d615f5e332fe9c/lib/core/connection/connect.js#L189.

Without the driver supporting this, there is no way for mongosh to support this functionality. While it does not seem to be an option that is very common, there is some evidence in SF and JIRA that we have customers using it. Given that supporting it should be pretty trivial, I would not drop this feature.

References:

• https://docs.mongodb.com/manual/reference/program/mongo/#cmdoption-mongo-tlscrlfile