There are few services we use that will be requiring TLS 2.1 instead of the current TLS 1.1.

Since we connect to these services using the WW.Client httpPost,etc, first I am assuming its ww.client that determines which version of TLS is implemented?

then, If that is the case, I am wondering at which version of ww.client did you implement TLS 2.1 ? I have 3 different versions.

If it is not the ww.client that sets the TLS version, then where is TLS version being set from?

Thanks

The HTTP features in Web Connection and the Client Tools are tied to Windows since it uses WinInet APIs from the WinApi.

There's more info in this blog post:

Web Connection and TLS 1.2 support

Although Web Connection is in the title this applies to the Client Tools as well.

+++ Rick ---

Looks like we are going to be OK with windows 10 already being TLS 1.2 compliant.

Would you consider adding a module to your Clients Tools that would run from user's system and make Windows 7 or Windows Servers TLS 1.2 compliant? (using the Registry modifications approach).

I be the first customer to download it!

Would you consider adding a module to your Clients Tools that would run from user's system and make Windows 7 or Windows Servers TLS 1.2 compliant? (using the Registry modifications approach).

No - I have no reliable way to test that and also I'm not keen on encouraging 10 year+ old software usage going forward. Additionally, it's a system fix that requires admin rights so not something that we'd want to do automatically or even as a utility.

You can write this yourself and add it to your applications if that's what you want to do. The Client Tools include a registry class that makes this easy.

+++ Rick ---