Salesforce will enforce a new permission boundary for the SOAP API login() operation on 1 December 2026. From that date, every user authenticating this way must have the Use Any API Auth user permission. Salesforce says the rule applies uniformly across all orgs and environments, including production and sandboxes. A request made by a user without the permission fails with INSUFFICIENT_ACCESS.
This is a focused access-control change, not the full retirement of SOAP API login(). It gives administrators a way to restrict a legacy authentication method to explicitly authorised identities. The method is still scheduled to be removed from API versions 31.0–64.0 with Summer ’27, so assigning the permission should be treated as a controlled bridge while affected integrations move to OAuth.
The date, scope and failure behaviour in this article are confirmed by Salesforce. The inventory, least-privilege and cutover recommendations are the Ostrelis view.
What changes on 1 December
Today, existing orgs can test the restriction through the relevant Release Update in Setup. It is already enabled by default in new orgs. On 1 December, the permission becomes mandatory everywhere for users that invoke SOAP API login().
The permission can be assigned through a profile or permission set, provided the user’s licence supports it. A dedicated permission set is normally easier to govern because it makes the exceptional access visible, reviewable and removable without changing a broad profile.
The rule applies to the authentication operation, not to all API activity. An integration may call login() once to obtain a session and then use REST, Bulk or SOAP operations. Classify the way the session is established rather than assuming that an integration is unaffected because most of its traffic is REST.
Keep the December controls separate
Salesforce has announced several controls around the same legacy authentication method. Mixing them together can produce an incomplete fix.
- 1 December 2026: the user needs Use Any API Auth for SOAP API
login()in all orgs and environments. Without it, Salesforce returnsINSUFFICIENT_ACCESS. - 15 December 2026 in sandboxes and 31 January 2027 in production: a separate rule requires a security token or mutual TLS when an org- or profile-level login IP range is broader than Salesforce’s stated thresholds. The related failure is
TOKEN_REQUIRED. - The same later rollout: Salesforce performs a one-time check and disables SOAP
login()in orgs with no activity through the method in the preceding six months. - Summer ’27: SOAP API
login()in versions 31.0–64.0 retires.
Granting Use Any API Auth therefore does not resolve a broad-IP-range problem, preserve an inactive method or make the integration ready for Summer ’27. Each control needs its own evidence and response.
Identify the identities that genuinely need it
Start with known integrations rather than assigning the permission to every API-enabled user. Review Login History, integration registers, middleware schedules, secrets inventories and supplier applications. Look for accounts used by ETL tools, desktop utilities, older managed packages, scripts and periodic data loads.
Ask the external-system owner how authentication occurs. A stored Salesforce username and password is a warning sign but not conclusive: it could indicate SOAP login(), the separately retiring OAuth username-password flow or another arrangement. Confirm the endpoint and handshake from configuration, logs, code or supplier documentation.
For every confirmed dependency, record the org, username, application, business process, owner, execution frequency, authentication method, API version and migration plan. Rarely run month-end, annual or disaster-recovery jobs deserve particular attention because a short activity sample can miss them.
Salesforce also documents a specific login status, LOGIN_ERROR_SOAP_LOGIN_REQUIRES_API_AUTH, for the missing-permission condition. Use that evidence to distinguish the new control from invalid credentials, IP restrictions and the security-token rule.
Assign the permission as a governed exception
Create a narrowly named permission set for confirmed SOAP login() identities and enable Use Any API Auth under System Permissions. Assign it only to the integration users that need the temporary bridge. Avoid adding it to a shared profile simply because that is quicker.
Before assignment, review whether each identity is dedicated to a single integration, whether it has more object or field access than necessary and who receives its failure alerts. The permission controls who may use the authentication method; it does not reduce the data access available after login.
Record an accountable owner and a target removal date for every assignment. If the account belongs to a person, challenge whether an unattended process should be using a human identity at all. Where several services share one username, separate them where practical so that ownership, monitoring and later migration can be managed independently.
Use the test run before enforcement
Salesforce provides a Release Update test run so teams can enable and disable the restriction before 1 December. Use it first in a representative sandbox, then test the complete integration process—not only whether authentication returns a session.
Run normal reads and writes, scheduled execution, bulk work, token or session renewal, error handling and monitoring. Confirm that operational teams recognise the INSUFFICIENT_ACCESS failure and know which permission set to inspect. For supplier-owned software, obtain the supported version and evidence that its authentication route has been tested.
Then test production deliberately during a controlled window. Inventory evidence can be incomplete, and switching on the restriction is a useful way to expose an overlooked dependency while rollback is still available through the test run. Set monitoring, named decision-makers and a clear end time rather than leaving an exploratory test running unattended.
A practical three-week plan
- Week one — discover: export login evidence, reconcile integration and supplier inventories, and classify the authentication handshake for every candidate.
- Week two — control: create the dedicated permission set, review each integration identity and assign only confirmed dependencies. Test the Release Update in a sandbox.
- Week three — prove: run controlled production testing, confirm alert routes and document the support response for missing-permission failures.
- Before 1 December — govern: publish the approved assignment list, owners, migration targets and removal dates. Recheck that no blanket profile assignment has been introduced.
This timetable is Ostrelis operational guidance, not a Salesforce requirement. A complex estate or slow-moving supplier may need a more intensive plan. The important point is to leave time for evidence and testing rather than treating the permission as an emergency checkbox on enforcement day.
Do not let the bridge become the destination
Salesforce recommends moving affected integrations to OAuth using external client apps. Appropriate server-to-server patterns can include client credentials or JWT bearer, depending on identity, secret and certificate requirements. The target should be selected from the use case and tested through the full business process.
Assigning Use Any API Auth keeps a confirmed dependency operating after 1 December; it does not extend the Summer ’27 retirement. Put the migration work into the same record as the temporary permission, with a technical owner, supplier dependency, test environment and production cutover date.
The Ostrelis view
The safest response is neither to refuse every assignment nor to grant the permission widely. Use the deadline to build an evidence-backed allowlist of identities that still depend on SOAP login(), give each one an owner and make its exit plan visible.
This is also a useful test of integration governance. If a platform team cannot tell which system uses an identity, how it fails or who can change it, the permission decision is only the first risk to resolve.
Ostrelis can help organisations investigate authentication dependencies, review integration identities, coordinate suppliers and plan controlled OAuth migrations. See our Salesforce managed services, integration support and approach and experience. Need help getting prepared? Talk to a Salesforce expert.
Need help getting prepared?
Ostrelis can help assess whether this change affects your Salesforce environment, identify dependencies and plan the work needed to prepare safely.
Talk to a Salesforce expertSources
- API release notes — Assign Use Any API Auth Permission for SOAP login() — Salesforce Help — Release Notes (Winter ’27 release notes, accessed 12 November 2026)
- login() — Salesforce Platform API Developer Guide (Current developer documentation, accessed 12 November 2026)
- Platform SOAP API login() Retirement & new Security Requirements — Salesforce Help (Updated October 2026, accessed 12 November 2026)
- Salesforce Platform Security Requirement Updates — Salesforce Help (21 October 2026, accessed 12 November 2026)
- The Salesforce Developer’s Guide to the Winter ’27 Release — Salesforce Developers Blog (October 2026, accessed 12 November 2026)
