This example presents a self-registration using email for channel verification. The same self-registration process could be implemented using an mTAN/SMS phone-number for channel verification.
Simplified flowchart
Possible configuration for a user self-registration flow:
The flow demonstrates 5 steps with the following characteristics:
Step | Type | REST Calls |
1 | user data registration step | /public/user-self-registration/registration/data/ |
In the Demo configuration a few characteristics are demonstrated: The continue REST call ist required to proceed to the next step. | ||
2 | username generation step | None. This step is executed automatically after successful completion of the previous step. |
For more information on stealth . | ||
3 | email verification step | /public/user-self-registration/verification/email/otp/check/ |
For more details on how this protects against enumeration . | ||
4 | user data registration step | /public/user-self-registration/registration/password/ |
| ||
5 | user persisting step | None. This step is executed automatically after a successful completion of step 4. |
|
Form-based GUI for self-registration
- For the above example a form-based GUI is expected to guide the user through the following steps:
- 1.The user will provide a number of attributes including the email address.
- 2.The user provides the OTP from the channel verification message.
- 3.The user chooses a password.