Authentication methods
Last modified: July 7, 2025
Devart ODBC Driver for Salesforce offers three authentication methods to provide secure and flexible access to Salesforce data. You can select the authentication method that best suits your needs.
OAuth 2.0
OAuth 2.0 is the recommended authentication method for accessing Salesforce, as it provides secure, token-based access without exposing user credentials.
How it works
OAuth uses a browser-based flow to authenticate the user. Upon login, Salesforce issues an access token that the driver uses to establish connections.
Steps to use OAuth
1. Select OAuth 2.0 from the Authentication drop-down list when configuring Windows DSN for Salesforce.
2. When prompted, a browser window opens for Salesforce login.
3. Log in with your Salesforce username and password and authorize the application.
4. The driver retrieves and stores the access token for subsequent connections.
User ID, password, and security token
This method uses direct username-password authentication with an additional security token for API access.
Required credentials
- User ID: Your Salesforce username.
- Password: Your Salesforce account password.
- Security Token: A unique token sent to your email upon request or after a password reset.
Steps to configure
1. Select User ID and Password from the Authentication drop-down list when configuring Windows DSN for Salesforce.
2. Enter the following credentials in the corresponding fields:
- User ID
- Password
- Security Token
Note
If your organization requires a security token, append it to your password when entering it into the driver configuration dialog.
For example:
Password: MyPassword
Security Token: 123ABC
Entered Password: MyPassword123ABC
Trusted IP ranges (Token-free access)
Salesforce allows bypassing the security token requirement for connections originating from trusted IP ranges defined in the Salesforce settings.
How it works
Your Salesforce admin configures trusted IP ranges in the organization’s security settings.
Connections from these IPs authenticate with just the username and password, without requiring a security token.
When to use
For on-premises applications operating within known, secure network environments.