From June 2016 Salesforce will
begin disabling the TLS 1.0 encryption using a phased approach. As a
result Flexor Apex for Salesforce may fail to login.
Please update to Flexor version 2.1.148 or above to resolve this.
Please check if your version of Flexor
has this fix by reviewing the Release Notes page
(unless you have already been
given a specific version by support).
If Flexor Apex fails to login and you have updated Flexor (or cannot update Flexor), please first check the Status tab for the unsupported TLS 1.0 client as shown in the screen shot below. If this error is not visible please check other factors e.g. Salesforce credentials, API access enabled etc..
** Your Salesforce admin can also modify the Salesforce Login History to show TLS Protocol version to confirm if you need to make any client side changes. **
When attempting to log into Salesforce the Flexor Apex will display any errors on the Status tab. If you see the error in the screen shot below please follow the steps below to resolve the issue.
If this is not the error, please review the other FAQ's.
Flexor Apex Status - Unsupported Client TLS 1
Your Salesforce administrator may have activated the Salesforce
update that disables support for TLS 1.0, or it may have been activated
automatically. Please see the following Salesforce FAQ for further information.
Screen shot of Salesforce TLS 1.1 Update Activation Page
Please Right click on this link
and select "Save link as" or the appropriate option for your browser,
to download a file containing the changes above to your PC.
Once the file has downloaded, double click on the file and select Run on the dialogue box that appears.
Then click Yes on the window that appears next.
A message should appear confirming the registry changes have been added.
Once the Registry changes have been added, please Exit and Restart Flexor and check that Flexor Apex for Salesforce can now login correctly, as per the screen shot below.
If this does not resolve the issue please review the other Salesforce FAQ's or contact support.
Click here to return to the FAQ index.