-
I'm working with an organization on a Mirth implementation. I have access to a server that I've installed Mirth on for them. They have set up a Microsoft SQL Server Database on a different server that I don't have access to. I've been able to successfully connect Mirth to this SQL Server DB previously, but now they are needing to turn on forced encryption for security purposes. The problem is, whenever they turn on forced encryption, they are getting this error: I did some research, and added "encrypt=true;trustServerCertificate=true" to the connection string, but that's not working. Here is the full string: jdbc:jtds:sqlserver://SERVERNAME:PORT/DBNAME;encrypt=true;trustServerCertificate=true Any idea what I'm doing wrong, and what I can do to get this working? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
Wrong driver.
oops.. one sec. read too fast... lol. Let me fire up one of my test machines. |
Beta Was this translation helpful? Give feedback.
-
I threw this together with some chatGPT help mostly because adding a TLS cert to MSSQL was a tad more complicated than I thought it was due to its requirements for the certificate. https://github.com/pacmano1/Mirth-Snippets/blob/main/mirth_and_MSSQL_withTLS.md |
Beta Was this translation helpful? Give feedback.
I think you are on the right track,, the URL is for the jTDS driver but using the MS Driver options. The equivalent with jTDS for
encrypt=true;trustServerCertificate=true
should bessl=require
. For the driver to authenticate the certificate presented by the server would bessl=authenticate
.