Salesforce is moving toward mandatory secure authentication for every mobile app. Mobile SDK 14.0 adds support for Refresh Token Rotation (RTR) and DPoP token binding. RTR is being enforced for Salesforce owned apps and ISV apps. DPoP is generally available in Winter '27, and enforcement is tentatively expected in 2027. Upgrade now so your app keeps working when these controls take effect.
|
Security control |
What it is |
Why it is urgent to upgrade to Mobile SDK 14.0 |
|---|---|---|
|
Refresh Token Rotation (RTR) |
The server rotates refresh tokens on each use to prevent token reuse. SDK 14.0 hardens the SDK so rotation no longer causes accidental logouts. |
RTR on an older SDK - Users may be logged out unexpectedly, but they can log back in. |
|
DPoP token binding |
Cryptographically binds each session's tokens to the device, so a stolen token cannot be used elsewhere. |
Once DPoP is required for your app, sessions that use Bearer tokens are rejected. Users can't sign in until they're on a DPoP-capable build and their session is migrated or they log in fresh. |
It is critical that apps are upgraded now to ensure a smooth, gradual rollout and enough runway for users to move to the updated app before enforcement begins.
Upgrade your app to Salesforce Mobile SDK 14.0 as soon as possible - This positions your app to handle RTR and DPoP before enforcement begins. The security hardening for RTR requires no code changes — it is transparent once you are on 14.0.
Add a call to upgradeToDPoP (for example, when the app comes to the foreground, with no other network calls in flight) so users who are already logged in move to DPoP. If the first 14.0 release ships without this call, another app release is needed before enforcement to ensure your existing logged in users are not logged out.
Optional: Mobile SDK 14.0 uses DPoP by default for new logins. For a staged rollout, you can ship with useDPoP (Android) or usesDPoP (iOS) set to false and turn it on later. This setting doesn't get around a server-side requirement: once DPoP is required for your app, sessions that use Bearer tokens are rejected.
Communicate to your users that they must update to the latest version of your app on their devices - otherwise they will still be on an older, non-compliant build and will be logged out when the mandates take effect. To drive adoption, we recommend in-app messaging that notifies users when a newer version is available or a forced-update mechanism that requires users to update before continuing. This ensures your users move to the compliant build ahead of time rather than relying on them to update on their own.
Now: Plan and complete your upgrade to Mobile SDK 14.0.
After release: Publish the updated app and prompt users to update on their devices.
Before enforcement: Ensure you have migrated existing sessions to DPoP and the majority of your users are on the updated app. To track adoption, use your app store analytics or in-app analytics.
What happens to users already logged in when RTR is turned on?
If your app is on Mobile SDK 14.0, already-logged-in users are not affected — they stay signed in and do not need to re-authenticate. The 14.0 SDK handles token rotation transparently, so the transition is seamless. If your app is still on an older SDK version when RTR is enabled, those same users may experience unexpected logouts because the older SDK does not handle rotation correctly.
What happens to users already logged in when DPoP is turned on?
If your app is on Mobile SDK 14.0 and calls the SDK’s upgradeToDPoP API, users who are already logged in don’t have to log in again. Their existing session moves to a DPoP-bound session in place, without the user entering their credentials again. Salesforce may show an approval screen; approving it completes the migration. We recommend calling upgradeToDPoP when the app comes to the foreground, at a point when no other network calls are in flight. Migration doesn't happen on its own. If your app never calls upgradeToDPoP, users who logged in before the upgrade stay on Bearer tokens. Once DPoP is enforced, they're logged out with no way to sign back in. If your app is still on an older SDK version, the same thing happens to those users until the app is upgraded to Mobile SDK 14.0.
How do I upgrade to Mobile SDK 14.0?
The fastest way to upgrade your app to Mobile SDK 14.0 is to use our upgrade skill. See Upgrade with an Agent Skill.
005461448

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.