Thread Details

What's Happening

As of the Winter '26 (API v65) release,Salesforce is retiring the SOAP API's login() method. SOQL Studio uses the SOAP Login() method to logon to Salesforce when the org connection is defined with Username/Password authentication. Furthermore, Salesforce will start removing the login() method from older API versions (31-64) starting with the Summer '27 release. For more information, refer to the following Salesforce articles:

SOAP API login() Retirement
SOAP API login() Call in SOAP API Versions 31.0 Through 64.0 Is Being Retired (Release Update)

How Does This Impact SOQL Studio

In response to this announcement, we have made changes to SOQL Studiov2025.2, Build 311 to provide a temporary work-around that allows existing connections defined with Username/Password authentication to continue to function. We will remove the ability to create new connections with Username/Password authentication in a future release making OAuth the only authentication method available for new connections. Connections defined with Username/Password authentication will permanently fail when Salesforce removes the login() method from the older API versions, specifically API v64.

Note: Existing and new connections defined with OAuth authentication are not impacted by this announcement because they do not use the SOAP API's login() method.

Specific Version Impact

SOQL Studiov2025.2, Build 311 - Username/Password connections will use SOAP API v64 to login, all other API calls will be made using API v65 (Winter '26). The login() call will fail once Salesforce removes the login() method from the SOAP API.OAuth connections use the Web-Server flow with PKCE, per Salesforce best practice, and will continue to function normally.
Recommendation: reconfigure connections to use OAuth as the authentication method.

SOQL Studio v2023.1 - v2025.2, Build 310 -Username/Password connections will continue to function until Salesforce removes the login() method from the SOAP API, at which time they will fail. OAuth connections use the Web-Server flow with PKCE, per Salesforce best practice, and will continue to function normally.
Recommendation: reconfigure connections to use OAuth as the authentication method.

SOQL Studio v2021.1 - v2022.2 -Username/Password connections will continue to function until Salesforce removes the login() method from the SOAP API, at which time they will fail. OAuth connections use the User-Agent flow. Salesforce no longer a recommends using the User-Agent flow and has blocked it by default, though Orgs can re-enable the flow. OAuth User-Agent authentication will continue to function normally if it is enabled in the Organization.
Recommendation: reconfigure connections to use OAuth as the authentication method. For greater security,upgrade to a newer version of SOQL Studio that uses OAuth 2.0 Web-Server flow (v2023.1 - current)

SOQL Studio versions prior to 2021.1 - All connections will fail when Salesforce removes the login() method from the SOAP API. There is no work-around. As of Summer '27, support for these versions of SOQL Studio will be sunset.
Recommendation: Upgrade to the newest version of SOQL Studio.