PingOne DaVinci is a visual orchestration tool that allows developers to create complex identity workflows using a drag-and-drop interface. It simplifies the process of building custom authentication and authorization flows without requiring extensive coding knowledge. In contrast, traditional journeys rely on predefined templates and scripts, which can be limiting for organizations with unique requirements.
What is PingOne DaVinci?
PingOne DaVinci is a component of the Ping Identity platform that provides a graphical interface for designing and implementing identity workflows. Instead of writing code, developers can use pre-built components to create sophisticated authentication and authorization processes. This makes it easier to integrate with various systems and adapt to changing business needs.
What are the main differences between PingOne DaVinci and traditional journeys?
Traditional journeys in PingOne are based on predefined templates that cover common use cases such as user registration, login, and password reset. While these templates are useful for standard scenarios, they lack the flexibility required for more complex workflows. DaVinci, on the other hand, offers a visual, code-free approach to building custom workflows.
| Approach | Pros | Cons | Use When |
|---|---|---|---|
| Traditional Journeys | Easy to set up | Limited customization | Standard use cases |
| PingOne DaVinci | Highly customizable | Steep learning curve | Complex workflows |
When should you use PingOne DaVinci?
Use PingOne DaVinci when you need to create custom identity workflows that go beyond the capabilities of traditional journeys. This includes scenarios where you need to integrate with multiple systems, implement conditional logic, or enforce specific business rules.
When should you stick with traditional journeys?
Stick with traditional journeys when you’re dealing with standard use cases that are well-supported by the predefined templates. This approach requires less setup time and is suitable for organizations that don’t need extensive customization.
🎯 Key Takeaways
- Traditional journeys are easy to set up but offer limited customization.
- PingOne DaVinci is highly customizable but has a steeper learning curve.
- Choose DaVinci for unique identity requirements; use traditional journeys for standard use cases.
How do you implement PingOne DaVinci?
Implementing PingOne DaVinci involves several steps, including designing workflows, integrating with systems, and deploying configurations.
Designing Workflows
To design a workflow in DaVinci, follow these steps:
- Log in to the PingOne console.
- Navigate to the DaVinci section.
- Create a new workflow by selecting the appropriate template or starting from scratch.
- Drag and drop components to build your workflow.
- Configure each component with the necessary settings.
Here’s an example of a simple workflow that includes user registration and login:
Integrating with Systems
Integrating with external systems is crucial for creating comprehensive workflows. DaVinci supports integration with various systems through connectors and APIs. For example, you can integrate with a user directory to verify user credentials.
Deploying Configurations
Once you’ve designed and integrated your workflow, deploy it to the PingOne environment. This involves publishing the workflow and configuring any necessary settings.
Publish the workflow
Click the "Publish" button in the DaVinci editor.Configure settings
Set up any additional configurations required for your workflow.Test the workflow
Run through the workflow to ensure everything is working as expected.How do you implement traditional journeys?
Implementing traditional journeys is straightforward and involves selecting a template, configuring settings, and deploying the journey.
Selecting a Template
To select a template for a traditional journey, follow these steps:
- Log in to the PingOne console.
- Navigate to the Journeys section.
- Choose a template that matches your use case.
- Customize the template with your specific settings.
Configuring Settings
Configuring settings involves setting up parameters such as email templates, verification methods, and redirect URLs. Here’s an example of configuring an email template for user registration:
Deploying the Journey
Deploying the journey involves publishing the configuration and testing it to ensure everything is working correctly.
Publish the journey
Click the "Publish" button in the Journeys editor.Test the journey
Run through the journey to ensure everything is working as expected.What are the security considerations for PingOne DaVinci?
Security is a critical aspect of any identity orchestration solution. When using PingOne DaVinci, consider the following security best practices:
Validate Inputs
Always validate user inputs to prevent injection attacks. Use built-in validation functions provided by DaVinci to ensure data integrity.
Use Encryption
Encrypt sensitive data both in transit and at rest. DaVinci supports encryption protocols such as TLS for secure communication.
Regularly Review Configurations
Regularly review your workflow configurations to identify and mitigate potential vulnerabilities. Keep an eye out for outdated components and update them as needed.
What are the security considerations for traditional journeys?
Security considerations for traditional journeys are similar to those for DaVinci. Here are some key points to keep in mind:
Secure Templates
Ensure that the templates you use are secure and up to date. Avoid using templates with known vulnerabilities.
Validate Inputs
Validate user inputs to prevent injection attacks. Use built-in validation functions provided by PingOne to ensure data integrity.
Regularly Update
Regularly update your journeys to incorporate the latest security patches and improvements. Stay informed about security updates and apply them promptly.
How do you choose between PingOne DaVinci and traditional journeys?
Choosing between PingOne DaVinci and traditional journeys depends on your specific requirements. Here are some factors to consider:
Complexity of Workflows
If you need to create complex workflows with custom logic and integrations, DaVinci is the better choice. Traditional journeys are suitable for simpler, standard use cases.
Time to Market
Traditional journeys offer a faster time to market due to their predefined templates. DaVinci requires more time to design and implement custom workflows.
Skill Level
DaVinci requires a higher level of skill and understanding of identity workflows. Traditional journeys are easier to implement and require less technical expertise.
Real-world Examples
Here are some real-world examples of when to use PingOne DaVinci and traditional journeys:
Example 1: Custom Onboarding Workflow
A company needs to create a custom onboarding workflow that includes multi-factor authentication, role assignment, and system integration. DaVinci is the better choice for this scenario because it allows for extensive customization and integration capabilities.
Example 2: Standard User Registration
A company needs to set up a standard user registration process. Traditional journeys are suitable for this scenario because they provide predefined templates that are easy to configure and deploy.
Conclusion
Choosing between PingOne DaVinci and traditional journeys depends on your organization’s specific needs. DaVinci offers high flexibility and customization options, making it ideal for complex workflows. Traditional journeys, on the other hand, are easier to set up and are suitable for standard use cases. By considering factors such as workflow complexity, time to market, and skill level, you can select the right orchestration approach for your organization.
Get started with PingOne today and choose the approach that best fits your needs. Whether you opt for DaVinci or traditional journeys, you’ll benefit from a robust identity orchestration solution.
