Title: Error: The request was aborted: Could not create SSL/TLS secure channel when calling api.flexera.com
Introduction:
When making a call to api.flexera.com, the request will always fail, when the call is made from a Windows Server 2012 R2 machine. The resulting error will be similar to the following:
"The request was aborted: Could not create SSL/TLS secure channel"
Details:
This means that the following will not work on Windows Server 2012 R2.
1. The Flexera SaaS Manager (FSM) Ingestion utility.
2. The FSM Connector in the FNMS/ITAM Beacon
3. Any call made to api.flexera.com in a PowerShell script
api.flexera.com supports both TLS 1.2 and TLS 1.3. The following cipher suites are supported over TLS 1.2 on api.flexera.com:
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
These are known strong cipher suites (at the time of this writing). There are other cipher suites available for TLS 1.2, but most are considered weak. While Windows Server 2012 R2 does support TLS 1.2, it does not support these cipher suites, and as a result, calls made from Windows Server 2012 R2 can not be made.
Workaround:
There is no known workaround at this time as these cipher suites are not supported on Server 2012 R2. If it is necessary to make calls into api.flexera.com, then it will be necessary to make them from a newer operating system. Typically, Server 2016 or later, or Windows 10.
Additional information:
Note that calls to beta.api.flexera.com, beta.api.flexera.eu and api.flexera.eu would also exhibit the same behavior.
