still pretty new to SQL administration so please bear with me. We recently updated to SQL Server Management Studio 19 and have been running into issues.
The long and short of it is I am trying to get our custom DNS for our Databases functioning on SQL Server Management Studio 19, its my understanding that SSMS 19 added some extra security layers that are causing some issues.
We have some custom DNS names setup to connect to our AWS RDS connections, this worked without issue in SSMS 18. Our users would use short-name.mycompany.com to connect to the DB instances in previous SSMS versions, but in while testing 19, I noticed I was getting the following error.
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) (Microsoft SQL Server, Error: -2146893019)
SSMS Error 01
Doing research I found that I could resolve the above error by installing an SSL cert on our server and that I could get it from AWS. I downloaded and installed the Cert which gave a new error message when trying to use short-name.mycompany.com
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The target principal name is incorrect.) (Microsoft SQL Server, Error: -2146893022)
SSMS Error 02
When using the endpoint names as they show in AWS: AWS-Endpoint-name.xxxxxxx########.amazonaws.com works now that the cert is installed, but it is going to be unwieldy for our end users.
Endpoint Name
I've found the "work around" of selecting "trust certificate" in the connection settings for ssms 19, but I'd rather not rely on that.
Trust Certificate
That option also has the weird side effect of not allowing expired passwords to be reset by giving the same error message:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The target principal name is incorrect.) (Microsoft SQL Server, Error: -2146893022)
SSMS Error 03
It seems like we might be able to setup our own Cert that includes the short hand names and install that on the RDS databases, but before going down that path I want to know if I'm missing something obvious. Is there some way to get this to work or are my end users going to have to use the long endpoint names? Any help would be appreciated, please let me know if you have any questions.
