Description

In the following page of the Ops Manager documentation: https://docs.opsmanager.mongodb.com/current/tutorial/enable-ssl-for-a-deployment/#specify-the-ssl-settings
we explain the differences between Client Certificate Mode OPTIONAL and REQUIRED, both of which directly relate to the corresponding MongoDB parameter net.ssl.allowConnectionsWithoutCertificates. However, for backwards compatibility purposes, Ops Manager still uses the deprecated but equivalent parameter net.ssl.weakCertificateValidation to reflect this setting.

Can we please amend this first sentence to make mention of the MongoDB configuration parameter that will actually get used when this mode is changed? Example:

Specify whether client TLS/SSL certificates are optional or required for every MongoDB deployment in the project. 

Note: For backward compatibility purposes, Ops Manager will continue using the [net.ssl.weakCertificateValidation|https://docs.mongodb.com/manual/release-notes/3.0-compatibility/#tls-ssl-configuration-option-changes] parameter to implement this in the MongoDB configuration file. 

This will prevent confusion for users who wonder what keeps adding this old parameter when their deployments are managed by Ops Manager.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)