Loading

Test Your App for DPoP After Upgrading to MSDK 14.0

Julkaisupäivä: Oct 8, 2026
Kuvaus

Demonstrating Proof of Possession (DPoP)

 

To test DPoP on your app:

  1. 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.

  2. 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:

    1. 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.

    2. Install your Mobile SDK 14.0 build, with DPoP turned on, over it without logging out.

    3. 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.

    4. 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.

    5. 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.

Ratkaisu

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.

Knowledge-artikkelin numero

005461450

 
Ladataan
Salesforce Help | Article