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
- 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
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
http requests to https endpoint with invalid ssl certificate
MarHan
Member Posts: 34
Hey guys,
I'm communicating with a web service on a test system of one of our partners. This endpoint uses a self-signed ssl certificate for its https connection. When I browse to it using a browser, it gives me a warning that the certificate's issuer cannot be validated, but I can proceed ignoring it or creating an exception for it.
But from AL code, I haven't found a way to ignore that. It always gives me a "The SSL connection could not be established... The remote certificate is invalid..." error.
In production, I won't have the problem as the productive endpoint will have a proper certificate.
Can I somehow tell the AL code / the BC runtime to ignore certificate errors?
And no: Using .net dlls is not an option as we must be compliant with the "universal code initiative". So I can only use plain AL objects and functions.
Best regards
Markus
I'm communicating with a web service on a test system of one of our partners. This endpoint uses a self-signed ssl certificate for its https connection. When I browse to it using a browser, it gives me a warning that the certificate's issuer cannot be validated, but I can proceed ignoring it or creating an exception for it.
But from AL code, I haven't found a way to ignore that. It always gives me a "The SSL connection could not be established... The remote certificate is invalid..." error.
In production, I won't have the problem as the productive endpoint will have a proper certificate.
Can I somehow tell the AL code / the BC runtime to ignore certificate errors?
And no: Using .net dlls is not an option as we must be compliant with the "universal code initiative". So I can only use plain AL objects and functions.
Best regards
Markus
0