Does anyone have experience using TLS encryption with Dynamics GP? We have figured out that is can be done by updating the ODBC Native Client 11 to the latest version including TLS 1.2 and checking the box in the ODBC DSN to use strong encryption. Microsoft is adamant that doing this makes our system not a supported configuration and jeopardizes support. They maintain there is no supported way to encrypt data in transit when using GP.
According to Microsoft support:
Having anything check-marked in the ODBC DSN that Dynamics GP is using to connect to SQL Server it not a supported configuration.
I have pointed out to them that Microsoft has a standing recommendation that all server-to-server communication and all client machine communication with a Microsoft server be protected with TLS. It’s a little hard to see how the Modern Lifecycle policy that applies to Dynamics GP can possibly offer “support and servicing” to the year 2028 without some kind of encryption of data in transit. The support policy becomes a hollow promise if it is impossible to construct a system for GP with basic security. To simply say we don’t offer anything is not a helpful response.
We may go ahead and do TLS encryption anyway because it is such a necessary precaution in the modern world. Has anyone out there done this? And, have you had any problems?
Sohaib Cheema
785
User Group Leader
André Arnaud de Cal...
626
Super User 2025 Season 2
Martin Dráb
621
Most Valuable Professional