ping-identity
    Preparing search index...

    Function initializeProtectForJourney

    • Executes a Journey PingOneProtectInitializeCallback.

      This is the only Journey initialize path: the native initialize callback carries its own server-driven configuration, parsed from the direct output[] form or the MetadataCallback-derived form used by Marketplace and legacy trees, so this function deliberately takes no ProtectConfig argument. A tree whose initialize callback carries no parseable configuration fails natively as PROTECT_INITIALIZE_ERROR rather than falling back to app-supplied configuration.

      Parameters

      Returns Promise<ProtectJourneyResult>

      Resolves with { type: 'success' } when initialization completes.

      ProtectError with codes PROTECT_CALLBACK_NOT_FOUND or PROTECT_INITIALIZE_ERROR on native failure.

      import { initializeProtectForJourney } from '@ping-identity/rn-protect';
      await initializeProtectForJourney(journey);

      Journey-only: use startProtect for DaVinci flows and pre-flow initialization. Native initialization is once-only, so whichever initialize path succeeds first wins; a subsequent initialize applies only its behavioral-data resume/pause, not its identity configuration. Declare the Protect callback types in handledCallbackTypes when calling journey.next so the Journey module leaves the callback state untouched.