Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
SecurityProtocol.Tls12
Ueff62
Member Posts: 2
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.
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.
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!
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.
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.
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!
0
Best Answer
-
Developer101
Member Posts: 569
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 Kingdom0
Answers