Move from V2 to V3
V3 uses an AppKey and app version instead of the older owner ID, application name, version and secret integration. It also binds sign-in sessions to an installation key and verifies server responses.
Create a separate V3 test integration. Test all three sign-in methods you use, pause and ban behavior, expiry, device resets, logout, network loss, and update prompts. Do not silently change a V2 client to V3 by replacing only its base URL.
V2 remains documented under Legacy. V1 is archived under End of Support. The version labels do not delete old endpoints or migrate existing customer records by themselves. Plan your client rollout and communicate any future service retirement separately.
Keep the old integration working until your customers have a tested migration path. Pin the SDK version you ship so later beta changes cannot silently change your application.
Move one application first
Suppose MyApp already has 200 customers using its V2 license login. Keep that application and its customer records. Create a V3 test build using the AppKey for MyApp. Do not create a second application and expect the original licenses to appear there automatically.
Replace the integration, not just the URL
V2 initializes with owner ID, application name, version and secret. V3 uses AppKey and version, plus installation proof during authentication. Its session token and request signing are different. An old V2 SDK cannot speak V3 just because its base URL ends in /v3.
Download the current V3 SDK, follow its dependency instructions and make one successful test login. Check how the language exposes results and userData. Keep callbacks and UI updates appropriate to your framework.
Preserve customer access
Use the same license keys and usernames already stored on the original application. Existing password hashes must be verified by the server’s compatible password handling; customers should not need plaintext password exports. Check device bindings before shipping: a different identifier strategy can make an existing machine look like a new device.
A V2 online session is not a V3 session. The new build signs in again and enrolls its installation proof. Do not copy an old session token into the new client or silently reset all customer devices to hide a migration problem.
Test both releases together
- Sign in from the existing V2 release and the new V3 test release using separate test identities.
- Ban a test identity and confirm both versions reject its access.
- Repeat with pause, expiry and device replacement.
- Confirm cloud-variable values agree and read-only values reject remote writes.
- Check Allowed Versions before publishing. Add the new version while keeping the old version allowed for the planned transition.
- Check update links for Stable and Beta identities. Do not move every customer to the test channel.
- Keep the previous installer and deployment available until the new release is proven.
If something goes wrong
Record the response code and request ID. Stop rollout, restore the previous client release where appropriate and investigate using a test identity. Do not overwrite the live database with an older backup simply because a single client fails: new customer changes may have arrived since that backup.
V1 remains documented as End of support and V2 as Legacy. Those labels do not revoke customer access by themselves. Any future shutdown needs its own notice and migration deadline.

