Why is it when connecting to mongo atlas cluster for my application, tls options are not passed?

Just like this one?

Hi @sg_irz,

I’m not too sure if this is what you were after but as per the DNS Seed List Connection Format documentation:

Use of the +srv connection string modifier automatically sets the tls (or the equivalent ssl) option to true for the connection. You can override this behavior by explicitly setting the tls (or the equivalent ssl) option to false with tls=false (or ssl=false ) in the query string.

if this doesn’t answer your question, could you clarify which tls options this topic is about?

Regards,
Jason

Thanks @Jason_Tran

If I use this connection string for my application server. Will it be able to connect to my mongodb cluster? (even without passing through a client certificate)

Can we go back a step and clarify what you mean originally by “tls options are not passed”? From the screenshots you posted, it looks to me like a standard code example to connect to Atlas using C#, and I didn’t see any TLS options there. Did you modify this example code, added some options, and found that you cannot connect?

If you’re asking about whether you need to supply a TLS certificate to connect to Atlas, the answer is no. Atlas uses LetsEncrypt as certificate authority, and official drivers should be able to connect. The example code should have no trouble connecting to Atlas without passing any additional TLS options.

Can we go back a step and clarify what you mean originally by “tls options are not passed”? From the screenshots you posted, it looks to me like a standard code example to connect to Atlas using C#, and I didn’t see any TLS options there. Did you modify this example code, added some options, and found that you cannot connect?

No I did not modify this, this is straight from guide in connecting application to Atlas. Although I did not try to test this connection as I am just trying to compare a mongo atlas cluster to a self managed mongodb cluster.

Sorry for the confusion, I just need clarification for my self managed MongoDB if I am able to connect to my cluster (with TLS enabled) without having a client certificate for each of my application server. Just like how mongodb atlas is doing it. Based on reading MongoDB doc, I can do it but I have to pass the tlsInsecure=true option on my connectionstring which is not advisable on prod environment.

If you’re asking about whether you need to supply a TLS certificate to connect to Atlas, the answer is no. Atlas uses LetsEncrypt as certificate authority, and official drivers should be able to connect. The example code should have no trouble connecting to Atlas without passing any additional TLS options.

Based on this, can I replicate this (about not needing to supply a TLS certificate to connect on mongodb) on my self managed mongodb using LetsEncrypt as the certificate authority?