Q2

Why isn't the Salesforce connector working?

A2

• To be able to use the Salesforce connector, you have to install the Magic xpi app that is available from the Salesforce AppExchange. For information about installing the app, click here. (Since version: V4.5a)

• The Salesforce connector does not work if it is behind a proxy server that requires only basic authentication. When you are required to work behind a proxy server, the proxy settings need to be defined in the Magic.ini file to enable the validation of your Salesforce resource. You do this by creating the following entry in the [MAGIC_ENV] section of the Magic.ini file: HTTPProxyAddress = <ProxyAddress>:<Port>
  
  For example: 10.9.3.16:8080

• To be able to work with Linux and TLS 1.2, you need to add the following to the JVM_ARGS parameter in the MAGICXPI.INI file: -Dhttps.protocols=TLSv1.1,TLSv1.2

Q3

Why am I getting an error message when I try to configure the OAuth with my Salesforce resource?

A3

Make sure that your .NET framework is configured to support TLS 1.2.

.NET 4.0 does not enable TLS 1.2 by default. To enable TLS 1.2 by default:

In the following two registry keys, set the SchUseStrongCrypto DWORD value to 1:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319.

If these keys do not exist, create them. These changes can be made by using the following import file: https://help.salesforce.com/apex/HTViewSolution?id=000221207.

Note that these registry keys will enable TLS 1.2 by default in all installed .NET 4.0, 4.5, 4.5.1, and 4.5.2 applications on your system. These registry values will not have an affect on .NET applications that set the System.Net.ServicePointManager.SecurityProtocol value.

It is recommended to test this change before deploying it to your production servers.