ping-app-integration
Implementation skill for integrating Ping Identity into web, mobile, and application SDK experiences.
What this skill does for you: Generates app-side integration code — SDK wiring, OIDC/PKCE flows, token handling — and guides you through the SDK docs and troubleshooting where code generation alone is not enough. Primarily an artifact-generating skill.
Invocation
Invoke explicitly with /ping-app-integration or by saying "use ping-app-integration to...".
When to use this skill
- "Integrate Ping into my React app using the orchestration SDK"
- "Use the iOS SDK with AIC journeys"
- "Wire OIDC redirect into a mobile app"
- "Embed a journey in a webview"
- "Migrate from the ForgeRock SDK to the Ping SDK"
- "Add browser-based login to my web application"
- "Connect my Android app to a DaVinci flow"
- "App-side OIDC / OAuth configuration for PingFederate"
- "Redirect URI mismatch error in my app"
- "CORS error on the token endpoint"
When NOT to use this skill
- Platform setup or app registration (no code): use
ping-foundation.
- Designing the flow or journey itself: use
ping-orchestration.
- General onboarding orientation: use
ping-quickstart.
Multi-skill use cases
A complete app integration spans three layers — all are required for a production outcome:
| Layer |
Skill |
Typical tasks |
| 1. Platform setup + app registration |
ping-foundation |
Tenant setup, redirect URI registration, sign-on policy |
| 2. Journey or flow design |
ping-orchestration |
Journey nodes, DaVinci flows, MFA policy |
| 3. SDK / app-side implementation |
ping-app-integration (this skill) |
SDK install, init, auth flow, token storage |
Complete platform setup first, then flow design, then hand off to this skill for SDK wiring.
End-to-end example (Android + DaVinci on PingOne):
- Use
ping-foundation to register an OIDC application in PingOne, configure the redirect URI (myapp://callback), and note the client ID and environment ID.
- Use
ping-orchestration to build and test a DaVinci login flow with username/password and push MFA nodes.
- Use this skill (
ping-app-integration) to add the com.pingidentity.sdks:davinci and com.pingidentity.sdks:oidc dependencies, initialize PingOne.init(context) with the client ID and discovery endpoint, call PingOne.startAuthentication(activity), and handle the AuthResult.
Step 1: What are you trying to do?
| Task |
Curated reference |
| Overview: skill positioning, SDK landscape, integration lifecycle |
references/curated/app-integration-overview.md |
| Android SDK integration (Journey or DaVinci) |
references/curated/mobile-integration-basics.md |
| iOS Swift SDK integration (Journey or DaVinci) |
references/curated/mobile-integration-basics.md |
| React / JavaScript web integration |
references/curated/web-integration-basics.md |
| Generic OIDC web app or SAML integration |
references/curated/web-integration-basics.md |
| Browser-based redirect / hosted login |
references/curated/web-integration-basics.md |
| On-prem app integration (PingFederate, PingAccess) |
references/curated/web-integration-basics.md |
| Server-side / backend OIDC, M2M client_credentials, token exchange, CIBA, retry/429 |
references/curated/server-side-integration-basics.md |
| Troubleshooting, migration (ForgeRock → Ping SDK) |
references/curated/integration-troubleshooting-basics.md |
MCP execution
See references/runtime/mcp-preflight.md for MCP config and Cursor preflight steps.
Step 2: Retrieval escalation
- Curated anchors (
references/curated/) — load 1–3 max. Stop if sufficient.
- For deep implementation work, delegate to the companion SDK skills below.
Companion SDK skills — ping-sdk-agent-skills
For deep implementation work (full code scaffolding, collector rendering, migration automation), delegate to the specialist skills in the pingidentity/ping-sdk-agent-skills plugin:
| Specialist skill |
Platform |
ping-orchestration-sdk-router |
Detects platform (Android/iOS/JS) and routes — use first when platform is ambiguous |
ping-orchestration-android-sdk |
Android Kotlin / Jetpack Compose — Journey + DaVinci |
ping-orchestration-ios-sdk |
iOS Swift / SwiftUI — Journey + DaVinci |
ping-orchestration-reactjs-journey-sdk |
React + AIC Journey flows |
ping-orchestration-reactjs-davinci-sdk |
React + PingOne DaVinci flows |
ping-orchestration-javascript-sdk |
Angular / Vue / Vanilla JS |
forgerock-to-ping-journey-migration |
ForgeRock SDK → Ping SDK automated migration |
Install: https://github.com/pingidentity/ping-sdk-agent-skills
1---2name: ping-app-integration3description: Use when writing code or wiring an SDK to integrate Ping Identity into a web, mobile, or backend app — Android/iOS/JavaScript SDK installation, OIDC authorization code + PKCE flows, token management, ForgeRock-to-Ping SDK migration, and app-side troubleshooting (redirect_uri_mismatch, CORS, token refresh failures).4---56# ping-app-integration78Implementation skill for integrating Ping Identity into web, mobile, and application SDK experiences.910**What this skill does for you:** Generates app-side integration code — SDK wiring, OIDC/PKCE flows, token handling — and guides you through the SDK docs and troubleshooting where code generation alone is not enough. Primarily an artifact-generating skill.1112## Invocation1314Invoke explicitly with `/ping-app-integration` or by saying "use ping-app-integration to...".1516## When to use this skill1718- "Integrate Ping into my React app using the orchestration SDK"19- "Use the iOS SDK with AIC journeys"20- "Wire OIDC redirect into a mobile app"21- "Embed a journey in a webview"22- "Migrate from the ForgeRock SDK to the Ping SDK"23- "Add browser-based login to my web application"24- "Connect my Android app to a DaVinci flow"25- "App-side OIDC / OAuth configuration for PingFederate"26- "Redirect URI mismatch error in my app"27- "CORS error on the token endpoint"2829## When NOT to use this skill3031- Platform setup or app registration (no code): use `ping-foundation`.32- Designing the flow or journey itself: use `ping-orchestration`.33- General onboarding orientation: use `ping-quickstart`.3435## Multi-skill use cases3637A complete app integration spans three layers — all are required for a production outcome:3839| Layer | Skill | Typical tasks |40|---|---|---|41| 1. Platform setup + app registration | `ping-foundation` | Tenant setup, redirect URI registration, sign-on policy |42| 2. Journey or flow design | `ping-orchestration` | Journey nodes, DaVinci flows, MFA policy |43| 3. SDK / app-side implementation | `ping-app-integration` (this skill) | SDK install, init, auth flow, token storage |4445Complete platform setup first, then flow design, then hand off to this skill for SDK wiring.4647**End-to-end example (Android + DaVinci on PingOne):**48491. Use `ping-foundation` to register an OIDC application in PingOne, configure the redirect URI (`myapp://callback`), and note the client ID and environment ID.502. Use `ping-orchestration` to build and test a DaVinci login flow with username/password and push MFA nodes.513. Use this skill (`ping-app-integration`) to add the `com.pingidentity.sdks:davinci` and `com.pingidentity.sdks:oidc` dependencies, initialize `PingOne.init(context)` with the client ID and discovery endpoint, call `PingOne.startAuthentication(activity)`, and handle the `AuthResult`.5253## Step 1: What are you trying to do?5455| Task | Curated reference |56|---|---|57| Overview: skill positioning, SDK landscape, integration lifecycle | `references/curated/app-integration-overview.md` |58| Android SDK integration (Journey or DaVinci) | `references/curated/mobile-integration-basics.md` |59| iOS Swift SDK integration (Journey or DaVinci) | `references/curated/mobile-integration-basics.md` |60| React / JavaScript web integration | `references/curated/web-integration-basics.md` |61| Generic OIDC web app or SAML integration | `references/curated/web-integration-basics.md` |62| Browser-based redirect / hosted login | `references/curated/web-integration-basics.md` |63| On-prem app integration (PingFederate, PingAccess) | `references/curated/web-integration-basics.md` |64| Server-side / backend OIDC, M2M client_credentials, token exchange, CIBA, retry/429 | `references/curated/server-side-integration-basics.md` |65| Troubleshooting, migration (ForgeRock → Ping SDK) | `references/curated/integration-troubleshooting-basics.md` |6667## MCP execution6869See `references/runtime/mcp-preflight.md` for MCP config and Cursor preflight steps.7071## Step 2: Retrieval escalation72731. Curated anchors (`references/curated/`) — load 1–3 max. Stop if sufficient.742. For deep implementation work, delegate to the companion SDK skills below.7576## Companion SDK skills — `ping-sdk-agent-skills`7778For deep implementation work (full code scaffolding, collector rendering, migration automation), delegate to the specialist skills in the `pingidentity/ping-sdk-agent-skills` plugin:7980| Specialist skill | Platform |81|---|---|82| `ping-orchestration-sdk-router` | Detects platform (Android/iOS/JS) and routes — use first when platform is ambiguous |83| `ping-orchestration-android-sdk` | Android Kotlin / Jetpack Compose — Journey + DaVinci |84| `ping-orchestration-ios-sdk` | iOS Swift / SwiftUI — Journey + DaVinci |85| `ping-orchestration-reactjs-journey-sdk` | React + AIC Journey flows |86| `ping-orchestration-reactjs-davinci-sdk` | React + PingOne DaVinci flows |87| `ping-orchestration-javascript-sdk` | Angular / Vue / Vanilla JS |88| `forgerock-to-ping-journey-migration` | ForgeRock SDK → Ping SDK automated migration |8990Install: `https://github.com/pingidentity/ping-sdk-agent-skills`
pingidentity