Orchestration SDKs

Introducing PingOne DaVinci support

PingOne Android iOS JavaScript

The DaVinci module provides powerful orchestration capabilities with PingOne DaVinci. They enable you to consume DaVinci flows to meet your use cases, all while providing a native Android or iOS, or a single-page app JavaScript experience.

You have complete control of your UI, so you can create the tailored experience you desire for your end users, all while leaving the DaVinci module to do the heavy lifting of communication between your app and your DaVinci flows.

UI Development

You are in charge of the experience your end users have in your Android, iOS, or JavaScript (SPA) applications.

Theme and brand your app the way you want to, focusing on your application logic and letting the DaVinci module communicate with PingOne DaVinci.

Dynamically Updating of DaVinci Flows

The DaVinci module works with PingOne DaVinci server-driven orchestration. This means that as long as you don’t hardcode UI elements in your application, and you appropriately handle the collector types, then you can update your DaVinci flow without needing to update your app or redeploy to the app stores.

Your app responds to changes in your DaVinci flows, without redeploying.
Figure 1. Your app responds to changes in your DaVinci flows, without redeploying.

This saves time and enables you to control your application orchestration experience without unnecessary burden.

Flow collectors

DaVinci sends requests to the DaVinci module from UI-related connectors. This enables you to step through each piece of information, and gather information from your end users appropriately.

Step through flows and and collect input from your users.
Figure 2. Step through flows and and collect input from your users.

For example, if you created a DaVinci flow to register a user, and you used the HTTP Connector - Custom HTML Template capability:

  • First name, last name, and email address would be sent as the TextCollector type to your app, and you would determine the way in which you represented this field in your UI.

  • The password field would be sent as the PasswordCollector type.

  • Once the flow completes, PingOne sends back the necessary tokens, and the DaVinci module automatically stores, retrieves, and refreshes tokens as needed.

Token Management

The DaVinci module uses the OAuth 2.0 auth code flow, and support PKCE.

This method is the best practice for first-party applications. The SDK automatically handles token exchange for you, and also securely stores the tokens.

The DaVinci module handles token refresh automatically, so you don’t have to think about it.