[BUG] CN for x.509 connections
I don't think maybe when you upgraded your SSL as referenced in this post (https://studio3t.com/whats-new/ssl-protocol-security-upgrade/) you didn't catch all the edges.
I can't get newer versions of 3t client to connect to a replica set via x.509. Even with "allow invalid hostnames" checked. The "discovered" entries for the replica set are contained in the SAN part of the cert presented by each node. Mongo v3.4, same URI and certs connect just fine with older MongoChef 3.6. Happy to send along the certs and connection uri.
1
vote
Anonymous
shared this idea
Hi Anon, would you be able to send an email to our support AT Studio3t.com address so that we can look into this further for you? Are you still encountering the same issue? Let us know!