Salesforce Authentication Types

RazorSQL supports the following Salesforce Authentication Types:

OAuth Web Brower Login

This authentication type requires the Consumer Key / Client Secret for the External Client App or Connected App defined in Salesforce that grants RazorSQL the permission to interface with the Salesforce instance. Enabling PKCE in the OAuth settings for the Salesforce External Client App or Connected App makes the communication more secure.

It also requires the Callback URL defined in the same Salesforce External Client App or Connected App. The Callback URL needs to be a localhost callback URL with a specific port, such as http://localhost:9040

Once the required data is supplied and the Connect button is pressed, RazorSQL will launch a web browser for the user to authenticate against Salesforce. RazorSQL passes PKCE values to Salesforce so that the interaction is more secure. After authenticating, Salesforce will return an authorization code to the Callback URL. RazorSQL will listen on the Callback URL to receive the authorization code. Once RazorSQL has the authorization code, it will make another call to Salesforce to get an Access Token that allows the user to call Salesforce APIs.


OAuth Client Credentials

This authentication is the OAuth Client Credentials Flow. RazorSQL requires the Consumer Key / Client ID and Consumer Secret / Client Secret defined in the Exteral Client App or Connected App that gives RazorSQL permissions to interact with Salesforce. It also needs the Instance URL of your organization.


Access Token and Instance URL

Use this option if you can obtain a Salesforce Access Token manually. Once RazorSQL has the Access Token and the organization's Salesforce Instance URL, it can communicate with the Salesforce APIs.


SOAP API Login (Salesforce is retiring this on 06/01/2027)

The SOAP API Login option requires the user's Salesforce login id, password, and Salesforce security token. This method of authentication will no longer work as of June 1st, 2027.