So I looked through our internal notes and databases and the information was as ambiguous as the articles that you have discovered.
However, then I found this sentence about the Esri requirement:
This may have implications on FME’s Esri ArcGIS Online (AGOL) Feature Service format from the time it was introduced (circa FME 2014) until FME 2015.1.1 (when we upgraded to a Python version with TLS 1.2 support).
That's my bold highlighting, but I think that's the relevant part.
So right now I'm 90% sure you won't be able to connect using 2014. I'm 5% thinking you might get somewhere if you can change the Python interpreter under Tools > FME Options (although I'm not sure what options 2014 had). I'm also about 5% it might be a proxy issue. Do you have any proxy set up under Tools > FME Options? If so, what are they set to?
I'm going to check with a developer, but like I said, I think it's likely to be not possible in FME 2014.
So I looked through our internal notes and databases and the information was as ambiguous as the articles that you have discovered.
However, then I found this sentence about the Esri requirement:
This may have implications on FME’s Esri ArcGIS Online (AGOL) Feature Service format from the time it was introduced (circa FME 2014) until FME 2015.1.1 (when we upgraded to a Python version with TLS 1.2 support).
That's my bold highlighting, but I think that's the relevant part.
So right now I'm 90% sure you won't be able to connect using 2014. I'm 5% thinking you might get somewhere if you can change the Python interpreter under Tools > FME Options (although I'm not sure what options 2014 had). I'm also about 5% it might be a proxy issue. Do you have any proxy set up under Tools > FME Options? If so, what are they set to?
I'm going to check with a developer, but like I said, I think it's likely to be not possible in FME 2014.
I think I agree, that it's not possible. The environment I have to work in is (unnecesary) complicated, but no matter what I set the Proxy to (none, use system settings, fill in all the details manually) seem to make a difference.
I will try to see if I can change the Python interpreter, just to see if that makes a difference. But I think my main priority is going to be pushing the upgrade forward that has been in the pipeline for over a year now :-)
Tahnk you for looking into this though, that is much appreciated (at least now I know I'm not the only one thinking the available information is ambiguous 
). I'll post here when I know more about the python thing, that could be helpful for others as well.
I think I agree, that it's not possible. The environment I have to work in is (unnecesary) complicated, but no matter what I set the Proxy to (none, use system settings, fill in all the details manually) seem to make a difference.
I will try to see if I can change the Python interpreter, just to see if that makes a difference. But I think my main priority is going to be pushing the upgrade forward that has been in the pipeline for over a year now :-)
Tahnk you for looking into this though, that is much appreciated (at least now I know I'm not the only one thinking the available information is ambiguous ). I'll post here when I know more about the python thing, that could be helpful for others as well.
So I have not been able to replace the Python interpreter yet, so still not sure if that helps or not. But what is interesting is that I have another workspace that connects to an https webservice in order to get an access token, and that token is retrieved without a problem. That webservice also uses TLS1.2, at least in my browser.
It is of course possible that this one still supports the previous protocols and the others do not anymore, and in the handshake between webservice and FME it is decided to fall back on 1.1 or even 1.0 or something. Is there a way to log that? Or do I need Wireshark in order to see that? extremely slim change I'd be allowed to install Wireshark, but I can always ask...
So I looked through our internal notes and databases and the information was as ambiguous as the articles that you have discovered.
However, then I found this sentence about the Esri requirement:
This may have implications on FME’s Esri ArcGIS Online (AGOL) Feature Service format from the time it was introduced (circa FME 2014) until FME 2015.1.1 (when we upgraded to a Python version with TLS 1.2 support).
That's my bold highlighting, but I think that's the relevant part.
So right now I'm 90% sure you won't be able to connect using 2014. I'm 5% thinking you might get somewhere if you can change the Python interpreter under Tools > FME Options (although I'm not sure what options 2014 had). I'm also about 5% it might be a proxy issue. Do you have any proxy set up under Tools > FME Options? If so, what are they set to?
I'm going to check with a developer, but like I said, I think it's likely to be not possible in FME 2014.
Without changing the Python interpreter you are correct. I used https://www.ssllabs.com/ssltest to check the TLS versins supported by the servers that I could and could not connect to, and used https://www.howsmyssl.com/ to check FME (using a simple httpfetcher). FME 2014 only supports TLS 1.0, the server I could not connect to only supports 1.2, the server I could connect to supports 1.0, 1.1 and 1.2. So in the handshake between FME and the server 1.0 is agreed upon, and FME gets the results I need.
A test with 2019-2 had no problems with either server, but that was done from my personal private laptop. I will still see if I can get another Python interpreter.
Thanks for your time though, it's been hepful (even if it isn't really the answer I would ike to hear )
