Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
TLS1.2 in Classic
Cyberghost
Member Posts: 46
Hi
With various internet services changing to only allow TLS1.2 communications, does anyone know how to do the equivalent of
System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
in NAV2009, as this is a dotnet command which will not work in the classic environment.
We have a customer who this will affect who is currently in the process of an upgrade but it will not be in place in time to bypass this issue.
Cheers
Chris
With various internet services changing to only allow TLS1.2 communications, does anyone know how to do the equivalent of
System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
in NAV2009, as this is a dotnet command which will not work in the classic environment.
We have a customer who this will affect who is currently in the process of an upgrade but it will not be in place in time to bypass this issue.
Cheers
Chris
"When you eliminate the impossible, whatever remains, however improbable, must be the truth" - Sherlock Holmes
"God and developers are in a constant battle. Developments to make their applications more idiot-proof, and God to produce bigger idiots!"
"God and developers are in a constant battle. Developments to make their applications more idiot-proof, and God to produce bigger idiots!"
0
Best Answer
-
OptionsCyberghost
Member Posts: 46
We ended up going the route of creating a dll to handle the calls."When you eliminate the impossible, whatever remains, however improbable, must be the truth" - Sherlock Holmes
"God and developers are in a constant battle. Developments to make their applications more idiot-proof, and God to produce bigger idiots!"0
Answers
"God and developers are in a constant battle. Developments to make their applications more idiot-proof, and God to produce bigger idiots!"