When making a call to api.flexera.com, the request will fail when the call is made from a Windows Server 2012 R2 machine. The resulting error will be like the following:
"The request was aborted: Could not create SSL/TLS secure channel"
The following items will not work on Windows Server 2012 R2.
- The Flexera SaaS Manager (FSM) Ingestion utility
- The FSM Connector in the FNMS/ITAM Beacon
- 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 considered strong cipher suites (at the time of this writing). Other cipher suites are 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’t be made.
Workaround
Currently, there is no known workaround, as these cipher suites are not supported on Server 2012 R2. If calls to api.flexera.com are necessary, they must be made from a newer operating system, typically Server 2016 or later or Windows 10.
NOTE: Calls to beta.api.flexera.com, beta.api.flexera.eu, and api.flexera.eu will exhibit the same behavior.
