DaVinci and backend flows
For backend-initiated PingOne DaVinci flows, you use the direct API method to trigger flow orchestration without any user interface components. This is ideal for actions such as automated risk checks or account provisioning. You configure the flow to accept and return JSON data from the API. The flow terminates with an HTTP Connector node using the Send Success JSON Response capability to return data back to your backend.
If the flow requires further steps or is part of a larger journey, the response could include a flowResponse object with instructions for the next action.
Why use DaVinci backend flows
PingOne DaVinci backend flows (initiated through API calls) are designed for automation and background processing. The benefits include:
-
Security: Running logic on the backend protects sensitive business rules and data consistency, ensuring that critical security decisions are not exposed to or manipulated by the frontend environment.
-
Consistency: A single backend flow can serve multiple different frontends (web, mobile), providing consistency for identity logic regardless of the device.
-
Integration: Backend flows can connect incompatible systems or custom databases to orchestrate complex security responses across an entire environment.
-
Headless Operations: You can perform migrations or background account updates without interrupting a user session or forcing users to complete specific UI actions.
Backend use cases
The following table provides guidance on when to implement a backend orchestration solution compared to frontend solutions.
| Use case | Recommended method |
|---|---|
User login and registration |
Frontend (UI is required) |
Syncing data |
Backend (No UI needed) |
Risk Scoring in background |
Backend (invisible to the user) |