.
We are updating all of our Click Field Service Edge endpoint services to require Transport Layer Security (TLS) version 1.2 across all Click Field Service Edge regions by November 1, 2020 in 3 phases, as mentioned below. This will prevent customers still using TLS 1.1 from accessing some of their Click Field Service Edge services.
Please ensure that all of your client applications support TLS 1.2 before the specified timeline for each service below.


What is changing?
=============
Click, a Salesforce Company will remove the ability to use TLS 1.1 on all Click Field Service Edge endpoints across all regions. We will be utilizing Amazon TLS Policy ‘TLS-1-2-2017-01’ exclusively:

* Studio - All major web browsers already support TLS 1.2.
* Mobile - TLS 1.2 is available today in all currently supported releases of mobile operating systems.
* Integration - If you have an integration through a web service or REST API with Click Field Service Edge (eg. Incoming/Outgoing Messages). Please confirm your applications utilizes TLS 1.2.

Note: We are providing an extended period of time before disabling TLS 1.1 to allow for potential changes required.


When is this changing?
================
The removal of TLS 1.1 is planned for the following dates, per service:
* Sunday, May 31, 2020 - Studio & Mobile services on all environments (both Sandbox & Production).
* Sunday, September 6, 2020 - Integration services interface on Sandbox environments.
* Sunday, November 1, 2020 - Integration services interface on Production environments.


Why is this happening?
================
As Trust is our #1 value, Click, a Salesforce Company is focused on helping our customers improve their security by using the latest security protocols. The TLS 1.2 encryption protocol will help ensure that the highest security standards and the safety of your data are maintained.


What does this mean for me?
====================
After Click, a Salesforce Company disables TLS 1.1, any inbound connections to or outbound connections from your Click Field Service Edge tenants that rely on TLS 1.1 will fail. This will impact a number of Click Field Service Edge services (listed above in ‘what is changing’), including any service integrations.


What action do I need to take?
=====================
To avoid any service disruption, we advise you to review all your connections to your environment, including any integrations you may have and confirm that you are using TLS 1.2. In most cases no action will be required for Studio & Mobile services as TLS 1.2 is supported in all current browsers. The change we are making is to enhance the security of the infrastructure associated with your instance and is not optional.


For additional information of the Amazon TLS Policy, supported ciphers list, and more, please refer to this article:
* https://community.clicksoftware.com/s/article/Click-Field-Service-Edge-Disabling-TLS-1-1


Best Regards,
Click Support
Posted on Jun 3, 09:59 UTC

.
We are updating all of our Click Field Service Edge endpoint services to require Transport Layer Security (TLS) version 1.2 across all Click Field Service Edge regions by November 1, 2020 in 3 phases, as mentioned below. This will prevent customers still using TLS 1.1 from accessing some of their Click Field Service Edge services.
Please ensure that all of your client applications support TLS 1.2 before the specified timeline for each service below.


What is changing?
=============
Click, a Salesforce Company will remove the ability to use TLS 1.1 on all Click Field Service Edge endpoints across all regions. We will be utilizing Amazon TLS Policy ‘TLS-1-2-2017-01’ exclusively:

* Studio - All major web browsers already support TLS 1.2.
* Mobile - TLS 1.2 is available today in all currently supported releases of mobile operating systems.
* Integration - If you have an integration through a web service or REST API with Click Field Service Edge (eg. Incoming/Outgoing Messages). Please confirm your applications utilizes TLS 1.2.

Note: We are providing an extended period of time before disabling TLS 1.1 to allow for potential changes required.


When is this changing?
================
The removal of TLS 1.1 is planned for the following dates, per service:
* Sunday, May 31, 2020 - Studio & Mobile services on all environments (both Sandbox & Production).
* Sunday, September 6, 2020 - Integration services interface on Sandbox environments.
* Sunday, November 1, 2020 - Integration services interface on Production environments.


Why is this happening?
================
As Trust is our #1 value, Click, a Salesforce Company is focused on helping our customers improve their security by using the latest security protocols. The TLS 1.2 encryption protocol will help ensure that the highest security standards and the safety of your data are maintained.


What does this mean for me?
====================
After Click, a Salesforce Company disables TLS 1.1, any inbound connections to or outbound connections from your Click Field Service Edge tenants that rely on TLS 1.1 will fail. This will impact a number of Click Field Service Edge services (listed above in ‘what is changing’), including any service integrations.


What action do I need to take?
=====================
To avoid any service disruption, we advise you to review all your connections to your environment, including any integrations you may have and confirm that you are using TLS 1.2. In most cases no action will be required for Studio & Mobile services as TLS 1.2 is supported in all current browsers. The change we are making is to enhance the security of the infrastructure associated with your instance and is not optional.


For additional information of the Amazon TLS Policy, supported ciphers list, and more, please refer to this article:
* https://community.clicksoftware.com/s/article/Click-Field-Service-Edge-Disabling-TLS-1-1


Best Regards,
Click Support
Posted on Jun 3, 10:02 UTC