Encrypt and Trust Server Certificate doesn't take effect when using SSMS 20 Utility with -S -U flag

Tianlei Wang 0 Reputation points
2024-06-12T17:08:05.87+00:00

Hi, I recently updated SSMS 19 to 20, but I encountered a strange issue. When Using SSMS 20, I have a remembered profile with Encryption set to optional and enabled Trust Server Certificate, and connect will not show certificate not trusted. However, if I use the utility ssms.exe -S <server> -U <user>, this will show certificate not trusted.

I also tried with SSMS 19, seems the above two option takes effect. Is SSMS 20 utility not using the advanced settings anymore?

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,271 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Erland Sommarskog 106K Reputation points MVP
    2024-06-12T21:35:28.32+00:00

    They reworked the connection dialogue in SSMS 20, and SSMS (like all client APIs), now defaults to requiring an encrypted connection. The regular connection dialogue exposes the encryption options on the front page, but there a couple of places they still have to address.

    And one such place is when you use the command line to start SSMS. I have noticed this myself, but I don't think I have come around to bring it up with Microsoft. But they may still have it on their radar.

    0 comments No comments