MongoDB X.509 authentication needs a subject-to-user mapping review
MongoDB supports X.509 certificate authentication for clients and for internal authentication between members of replica sets and sharded clusters. The feature is useful when a workload should authenticate with a certificate instead of a shared password. It also moves several familiar identity questions into certificate and directory configuration, where they are easier to miss during a routine database review.
The database does not accept "a valid certificate" as a complete identity by default. A client presents a certificate during TLS, and MongoDB authenticates an external user derived from the certificate subject. That user exists in the $external authentication database. Authorization still comes from roles assigned to that user.…