Identity Orchestrator

Identity Orchestrator (IO) provides an intuitive, visual drag-and-drop interface for designing and managing user workflows without writing code. The flexible architecture enables you to create sophisticated scenarios by connecting pre-built nodes that handle everything from user authentication to API integrations. With Identity Orchestrator, you maintain full control over input and output structures, conditional branching, triggers, and execution logic across the entire process.

IO concepts

IO represents each operation as a node. Nodes perform specific tasks and are connected through directional links that define both the execution path and the data flow. To implement Identity Orchestrator:

1. Create flows visually using the drag-and-drop editor.
2. Link each node's input and output to define the execution sequence.
3. Specify the parameters and logic for each node.
4. View and manage flow variables in test environments.
5. Activate validated flows for production use.

Each flow execution creates a unique session that:

1. Stores flow state and variables
2. Manages user context and authentication
3. Persists data across node executions
4. Expires based on configured Time To Live (TTL)
5. Provides isolation between concurrent executions

IO components

The core components of Identity Orchestrator are:

Flows

A flow is a structured pipeline composed of ordered processing steps. Each step executes a specific operation, such as: data transformation and validation, authentication and authorization, conditional routing, and integration with external systems.

Flows define the execution logic, data propagation rules, and conditional branching, to enable automated and consistent processing across the entire pipeline. Flows are executed in response to user actions or system events.

Nodes

A node is a single, self-contained step within a flow. IO connects nodes together to form identity and access processes that are tailored to an organization's requirements.

Nodes are used to create, customize, and manage flows. Each node performs a specific function, such as collecting user input, stores variables for use by subsequent nodes, and passes the result to the next node in the flow.

Vaults

A vault stores values used by flows. Vaults let you organize secrets and variables in your domain and make them available to the flows that need them.

Benefits of IO

Rapid prototyping and testing:

• Standardized workflow architecture and management
• No coding required: Build complex workflows visually
• Connect to any API or service: Web hook support for server-to-server integration.
• Multi-tenant architecture: Independent session management, customized flows for each tenant, and isolated data storage
• Mult-language ssupport: Dynamic language selection, user-agent based defaults, and complete UI translation support
• Share flows among tenants/environments: Export flows as JSON files, and import flows with optional ID preservation
• Brand-styling, logo, and color: Custom CSS per flow or node and responsive design support
• Real-time execution: Immediate processing of session updates
• Reduced time-to-market: Deploy new journeys quickly

Easy maintenance:

• Self-documenting visual flows
• Version control: Manage and test multiple flow versions, restore previous versions, and view version history
• Audit trail of user journeys
• Step-by-step flow execution: Inspect variables and view error-tracking and execution logs