
DaVinci's Challenge Connector
Date Posted:
20 Aug 2025
Category:
Security

DaVinci's Challenge Connector
Date Posted:
20 Aug 2025
Category:
Security

DaVinci's Challenge Connector
Date Posted:
20 Aug 2025
Category:
Security
DaVinci's Challenge Connector - Enabling Asynchronous Workflows
Introduction Of DaVinci's Challenge Connector
PingOne DaVinci is a no-code identity orchestration tool that helps you construct secure and smooth user journeys. Connectors serve as the foundation of these excursions. Connectors are pre-built connectors that link DaVinci to third-party services, other Ping products, HTML pages, and a variety of tools. Each connector includes one or more capabilities that can be used as "nodes" in your flow, allowing you to create complicated workflows using a drag-and-drop interface.
Challenge Connector
This connector lets you branch your DaVinci flow for external events like MFA. By using this connector you can show user an waiting message on the main flow, while the secondary flow interact with user with elsewhere. When secondary flow completed the challenge connector will continue to main flow. Your flow's challenge is created, updated, or checked by the connector. Challenges are special variable that can be created by several connector's, including the Challenge connector, Flow Conductor, and some authentication and verification connector's. Other connectors, like HTTP, can pause flow until a challenge changes.
Steps to create Challenge Connector
Go to Admin console > DaVinci > Flows > Add Flow.
Give a Name of this flow.
Go to the end of node and drag to choose the Add Connector
Select Challenge to add the card.
Now select Add Transaction Status capability.
Disable the Is challenge record complete.
Select the Challenge Status as started.
Click Apply.
Now add the HTTP connector
Select Custom Html Message to show the status of waiting message and also select the skpolling.
In Challenge attribute select the challenge variable which contains the challenge connector node data.
Finally select Enable Polling for html page.
After this add any MFA connector and choose the desired variables to authenticate.
Choose another challenge connector and select Update Transaction Status.
Under the Challenge variable select the connection as challenge.
Enable the Is challenge record complete.
Select the Challenge Status as approved and add an custom message using HTTP connector and click Apply to deploy the flow.










Conclusion
The PingOne DaVinci platform provides a versatile and powerful solution to create sophisticated identification workflows with a diverse set of connectors. The Challenge connection, in particular, is critical for coordinating asynchronous tasks. Using this connection to handle the state of a "challenge" variable allows you to construct seamless user experiences with several, independent steps, such as those required for multi-factor authentication. This functionality ensures that user journeys stay smooth and secure even when waiting for external events to occur.
Stay tuned to our blog to see more posts about
Sailpoint products implementation and its related updates.
Stay tuned to our blog to see more posts about
Sailpoint products implementation and its related updates.
Category:
Security
Stay tuned to our blog to see more posts about
Sailpoint products implementation and its related updates.
Stay tuned to our blog to see more posts about
Sailpoint products implementation and its related updates.
Category:
Category:
Security
Security
Get your
Tailored Quote for your
Organisation
Get your
Tailored Quote for your
Organisation
DaVinci's Challenge Connector - Enabling Asynchronous Workflows
Introduction Of DaVinci's Challenge Connector
PingOne DaVinci is a no-code identity orchestration tool that helps you construct secure and smooth user journeys. Connectors serve as the foundation of these excursions. Connectors are pre-built connectors that link DaVinci to third-party services, other Ping products, HTML pages, and a variety of tools. Each connector includes one or more capabilities that can be used as "nodes" in your flow, allowing you to create complicated workflows using a drag-and-drop interface.
Challenge Connector
This connector lets you branch your DaVinci flow for external events like MFA. By using this connector you can show user an waiting message on the main flow, while the secondary flow interact with user with elsewhere. When secondary flow completed the challenge connector will continue to main flow. Your flow's challenge is created, updated, or checked by the connector. Challenges are special variable that can be created by several connector's, including the Challenge connector, Flow Conductor, and some authentication and verification connector's. Other connectors, like HTTP, can pause flow until a challenge changes.
Steps to create Challenge Connector
Go to Admin console > DaVinci > Flows > Add Flow.
Give a Name of this flow.
Go to the end of node and drag to choose the Add Connector
Select Challenge to add the card.
Now select Add Transaction Status capability.
Disable the Is challenge record complete.
Select the Challenge Status as started.
Click Apply.
Now add the HTTP connector
Select Custom Html Message to show the status of waiting message and also select the skpolling.
In Challenge attribute select the challenge variable which contains the challenge connector node data.
Finally select Enable Polling for html page.
After this add any MFA connector and choose the desired variables to authenticate.
Choose another challenge connector and select Update Transaction Status.
Under the Challenge variable select the connection as challenge.
Enable the Is challenge record complete.
Select the Challenge Status as approved and add an custom message using HTTP connector and click Apply to deploy the flow.










Conclusion
The PingOne DaVinci platform provides a versatile and powerful solution to create sophisticated identification workflows with a diverse set of connectors. The Challenge connection, in particular, is critical for coordinating asynchronous tasks. Using this connection to handle the state of a "challenge" variable allows you to construct seamless user experiences with several, independent steps, such as those required for multi-factor authentication. This functionality ensures that user journeys stay smooth and secure even when waiting for external events to occur.