forgerock-to-ping-journey-migration
ForgeRock → Ping Journey SDK Migration
Help a developer move an existing app off the legacy ForgeRock SDK and onto the new Ping Identity Journey SDK. This skill drives a careful, auditable migration: scan the codebase, preview the plan, comment-out-and-replace (never silent delete), verify the build, and leave behind a report the developer can hand to a reviewer.
Supported platforms
| Platform | Legacy package | New package | Reference |
|---|---|---|---|
| Android (Kotlin) | org.forgerock:forgerock-auth (FRAuth/FRSession) |
com.pingidentity.sdks:journey |
android-migration.md |
| iOS (Swift) | ForgeRock/forgerock-ios-sdk (FRAuth/FRUser) |
ForgeRock/ping-ios-sdk (PingJourney/PingOidc) |
ios-migration.md |
| JavaScript/TypeScript | @forgerock/javascript-sdk |
@forgerock/journey-client + @forgerock/oidc-client |
javascript-migration.md |
Each reference file is a complete before/after mapping (imports, classes, methods, parameter changes). Load only the file(s) that match the detected platform(s) — do not pre-read all three.
When to trigger
Fire this skill whenever the user indicates they want to port ForgeRock auth code to the Ping SDK, even without using the word "migrate". Examples of triggering phrases: "we need to move off FRAuth", "convert this to journey-client", "what would it take to upgrade our ForgeRock integration", "replace FRSession.authenticate with the new SDK". When in doubt, offer — being slightly pushy here is correct because the user already has legacy code on disk that will break when ForgeRock is sunset.