Orchestration SDKs

Try out the Journey module for JavaScript

PingOne Advanced Identity Cloud PingAM JavaScript

In this tutorial you configure and run the reactjs-todo-journey sample ReactJS single-page app, and make use of a Node.js REST API server backend app.

The sample supports many of the callbacks used by authentication journeys in Advanced Identity Cloud and PingAM, including advanced use cases such as external IdP integration and PingOne Protect.

What does the reactjs-todo-journey sample support?
Feature Supported by sample

Orchestration

  • Advanced Identity Cloud/PingAM - Journeys

Implementation

  • Embedded

Language

  • ReactJS

Callbacks

  • BooleanAttributeInputCallback

  • ChoiceCallback

  • ConfirmationCallback

  • KbaCreateCallback

  • NameCallback

  • PasswordCallback

  • PingOneProtectEvaluationCallback

  • PingOneProtectInitializeCallback

  • RedirectCallback

  • SelectIdPCallback

  • StringAttributeInputCallback

  • TermsAndConditionsCallback

  • TextOutputCallback

  • ValidatedCreatePasswordCallback

  • ValidatedCreateUsernameCallback

  • WebAuthn (Register/Authenticate)

Integrations

  • PingOne Protect
The to-do sample app
Figure 1. Screenshot of the to-do page of the sample app

Before you begin

Before you begin this tutorial ensure you have set up your PingOne Advanced Identity Cloud tenant or PingAM server with the required configuration.

For example, you will need to configure CORS, have an OAuth 2.0 client application set up, as well as an authentication journey for the app to navigate.

Complete prerequisites

Step 1. Download the samples

To start this tutorial, you need to download the SDK sample apps repo, which contains the projects you will use.

Start step 1

Step 2. Configure connection properties

Configure both the Todo client app, and the API backend server app to connect to the OAuth 2.0 application you created in PingOne Advanced Identity Cloud or PingAM.

Start step 2

Step 3. Test the app

In this step you run the sample applications, authenticate as a user, view the tokens and user info, and then end the session by signing out.

Try it out