Salesforce retires SOAP login(): first breakages 31 January 2027
Keep the integrations you cannot rewrite signing in to Salesforce.
A small self-hosted bridge answers the retired login() call and the OAuth password grant, and hands back a token from Salesforce's own JWT flow. Change one setting in the old software: its login URL. Nothing else.
- 31 Jan 2027 login() starts failing in production orgs
- 20 Feb 2027 the OAuth username password flow is switched off
- Summer '27 login() is removed for API 31 to 64
How it works
- Your legacy client calls
login()on the bridge, with a bridge password instead of the Salesforce one. - The bridge checks that password locally. A wrong one never reaches Salesforce.
- It gets an access token through an External Client App your admin created, using Salesforce's JWT bearer flow.
- It returns a normal
LoginResult. Every data call then goes straight to Salesforce; the bridge never sees your records.
Because the bridge never calls login() itself, you can switch login() off in your org today and keep the legacy client working.
What works
| Client | Status |
|---|---|
| Data Loader (batch mode) | Verified with 64.1 |
| Java and .NET clients built from the Partner or Enterprise WSDL | Verified Java at API 31, 40, 64 |
| Password grant clients: jsforce, restforce, Apache Camel | Supported, token URL is configurable |
| Vendor packages with a configurable login URL | Expected to work; test in a sandbox first |
| simple-salesforce, Microsoft Entra provisioning, anything with login.salesforce.com hard coded | Not supported |
API versions 31 to 40 have a second deadline. Salesforce deprecates them from Summer '27 and retires them in Summer '28. A v31 to v40 client keeps working through the bridge until then; after that its data calls fail and no bridge can help. Plan to move those clients to a newer WSDL version.
Pricing
Self-hosted
$1,990 per production org per year
or $199 per org per month. Launch price $1,490 a year for annual plans bought before 31 January 2027.
- Sandboxes free
- Unlimited integration users
- Admin page, audit log, setup guides
- Email support, reply within two business days
- 14 day refund
Hosted Coming soon
$499 per month
We run the bridge for you; nothing to install. Request it now and lock a founding rate of $399 a month for the first year.
Finding self-hosted too technical? This is the route for you.
Enterprise
Multiple orgs, a contract, a security review, or embedding in your product? Request enterprise access.
Five org packs sell at list through the normal checkout above.
Start in a sandbox, free
Every buyer tests in a sandbox first, so sandbox licences cost nothing. Enter your production or sandbox My Domain and we email a 90 day key for that org's sandboxes.
Guides
Security
- No Salesforce password is stored outside Salesforce. Legacy clients use a separate bridge password, kept only as a hash.
- Access your admin controls. The bridge gets tokens through an External Client App your admin created and can revoke at any time.
- Salesforce's recommended flow. JWT bearer, signed with a key that never leaves your server.
- Holds no data. The bridge sees one login per session; records go directly between your client and Salesforce.
- Audit log. Every login attempt, exportable as CSV, with no passwords or tokens in it.
- login() can be off. The bridge does not use it, so you can disable it org wide.
Questions
What counts as an org?
One production Salesforce org, identified by its My Domain. Its sandboxes are included free. A key covers the orgs listed at purchase.
What happens when my subscription renews or ends?
The bridge fetches renewed keys by itself. If a subscription ends, the bridge keeps working for 14 days with warnings, then stops answering logins. Your config and logs stay with you.
Can you migrate our integrations instead?
No. We sell the bridge and support its configuration. A Salesforce consultancy is the right partner for rewrites.
Refunds?
Within 14 days, no questions asked.