Net-based applications while 'raw' requests (via curl. What could be causing this TLS connection error from. I don't find any indication that the problem is related to the certificates being used. The cipher being used for the TLS connection is in the allowed set defined in the registry (\SYSTEM\CurrentControlSet\Control\Cryptography\Configuration\Local\SSL\00010002). I've been unable to identify the cause of the error. The fact that the curl request succeeds leads me to think that the problem is not related to a certificate issue or something related to the networking infrastructure between the windows web server and the windows/linux api servers. However, sending that same REST request using curl.exe (mingw library) from a command prompt succeeds with no error. Invoke-RestMethod), I receive the same TLS channel error. Some older libraries may not support TLS 1.2 and need to be upgraded or require TLS 1.2 to be selectively enabled. Confirm your HTTPS library supports TLS 1.2.
Some languages may have bugs preventing SSL negotiations to connect with TLS 1.2, even with it enabled and set as preferred. If I send the same API request in Powershell (e.g. Many older versions require specific commands to enable TLS 1.2. I'm using TLS 1.2 for these REST requests. The web application sends REST requests to the API services, but I receive this error: "Could not create SSL/TLS secure channel". I'm working on a product that is deployed in a FedRAMP environment and consists of a mix of API services implemented on Windows and Linux as well as a web application running on IIS.
0 kommentar(er)
