Flow design
Flows are designed (or defined) in the configuration using the Config Editor. In addition to selecting steps and putting them in a particular order, additional flow concepts like various types of conditions, selection, goto, and dynamic step activation allow modeling more complex flows.
The mentioned flow concepts are explained in detail in this chapter.
Consider the following example showing a very simple 2-factor authentication flow in the Config Editor:
Flows and REST APIs
Flow steps can be interactive and non-interactive. While non-interactive steps are simply processed, the interactive ones expose REST API end-points (see REST API specification for details). The flow state machine in IAM enforces a valid sequence of steps and expects the REST client to act accordingly.
Consider the following password reset flow example:
More details can be found in the sub-sections of this chapter.
Further information and links
- More usage examples can be found in:
- ●Loginapp module: 17.2. Loginapp REST API
- ●Transaction approval module: 20.1. Transaction approval REST API