Demonstrating Proof of Possession (DPoP)
To test DPoP on your app:
Test fresh DPoP logins. Mobile SDK 14.0 ships with DPoP already turned on for the client. Log in to your app against your existing Salesforce org and connected app (CA) or external client app (ECA). Confirm that login and API calls succeed. You don't need a CA or ECA configured to require DPoP for pre-release testing. A CA or ECA that doesn't require DPoP still validates DPoP proofs when they're present, so this test runs the full DPoP flow on the client.
Test migrating existing sessions to DPoP. Users who logged in before the upgrade still have Bearer-token sessions. These sessions move to DPoP only when your app calls upgradeToDPoP. To test the migration:
Start your app on a Bearer session. You can get one from your current (pre-14.0) production build, or from a 14.0 build with useDPoP (Android) or usesDPoP (iOS) set to false.
Install your Mobile SDK 14.0 build, with DPoP turned on, over it without logging out.
Trigger your app's upgradeToDPoP call. For example, if you call it when the app comes to the foreground, send the app to the background and bring it back.
Confirm the user isn't asked to enter credentials again. If an approval screen appears, approving it completes the migration. Confirm the session is now DPoP-bound and later API calls succeed. To check that the session is DPoP-bound, confirm that the user's credentials have tokenType "DPoP", or that the ftr_ segment of the SDK User-Agent includes DP.
Trigger the migration while background sync or other requests are running, and confirm that your app waits for them to finish or skips the migration until later.
Test basic functionality. Confirm that data syncs, reads, and writes keep working with both a fresh DPoP session and a migrated one.
Test custom networking. If your app makes authenticated calls outside the SDK's REST client, test those calls with a DPoP session. These requests must use DPoPRequestDecorator, or they fail once the session is DPoP-bound.
Test WebView sessions. If you have a hybrid remote app or your app uses WebViews, test that the WebView session starts correctly through frontdoor or cookie injection. For DPoP sessions, this now relies on ui_sid.
Regression:
Verify that core app flows—such as data access, logout, reauthentication, and offline sync (if applicable)—behave as expected after the upgrade.
Test your app across the platforms and versions that your users run. If you support both iOS and Android, validate the login flow on each operating system.
005461450

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.