TLS 1.2 and Web Services

(0) Share

Report

Posted on by Kaylasch

245

Hello,

I have a customer that uses Nodus for credit card encryption, and they require TLS 1.0 and 1.1 to be disabled to maintain PCI compliance. This customer is also coming off of Business Portal PO to Web client/PO Workflow in GP, and needs email approval available. We are currently performing a production upgrade to GP 2018.

The following article says web client works, but web services does not, and that it is being worked on. Is there a fix for web services, or will they need to go without email approval?

https://community.dynamics.com/gp/b/dynamicsgp/archive/2018/02/16/dynamics-gp-and-tls-1-0

*This post is locked for comments

All responses (2)

Answers (0)

Suggested answer

Talon Meyer 91 on at

Like (2)

Report

RE: TLS 1.2 and Web Services

It is true that GP Web Services installation requires TLS 1.0 when using a SQL authorization store.

I did find a workaround to keep TLS 1.0 disabled and complete the installation. I logged onto the server with a local machine account instead of a domain account, completed the installation, and then used Notepad++ to mass modify the .config files to use the domain service account I wanted. At this point I was able to open the GP Web Services configuration panel with a domain account and complete the setup.
Suggested answer

Beat Bucher GP Gee... 28,021 Super User 2024 Season 1 on at

Like (0)

Report

RE: TLS 1.2 and Web Services

Hi @Kaylasch,

This blog post from the Microsoft support team should answer most of your questions : community.dynamics.com/.../dynamics-gp-and-tls-1-0

The truth is that Web Services will no longer work without TLS 1.0

dynamicsgpblogster.blogspot.com/.../microsoft-dynamics-gp-and-tls-10.html

technologyblog.rsmus.com/.../gp-web-services-and-tls-1-0