SecurityProtocol.Tls12

Ueff62
Ueff62 Member Posts: 2
in NAV Three Tier
We made integration for one of our clients and everything was great 😊
But recently the integration stopped working, as it turned out on the other side they changed the Tls protocol. They changed 1.2 and added 1.3.
yg43cm68gjs7.png

NAV2017 -
ServicePointManager.SecurityProtocol(SecurityProtocol.Tls12);
The client's operating system is Windows Server 2016, as far as I understand we can't use 1.3.

Tried changing the queuing in Ciper Suite Order but that didn't help.
aiwora5bkqdi.png

From the list of protocols to be supported, we have the first two, but no third protocol - ECDHE - RSA - CHACHA20 - POLY1305

Is there any ideas to solve this problem, any help would be greatly appreciated. Thank you!

Best Answer

  • Developer101
    Developer101 Member Posts: 569
    Answer βœ“
    I have seen this issue before and tried everything. At the end it has been decided to update windows server version which customer will handle internally.
    United Kingdom

Answers

  • Developer101
    Developer101 Member Posts: 569
    Answer βœ“
    I have seen this issue before and tried everything. At the end it has been decided to update windows server version which customer will handle internally.
    United Kingdom
  • Ueff62
    Ueff62 Member Posts: 2
    Thank you for your reply. So far we have settled on the option of making a PROXY API and working through it.

Categories