Condition Email Verification
Overview
The main task of this execution is to allow the next flow to continue only if the user’s email is verified. If not, it skips the conditional check and moves to the next step. It can be changed in the authenticator config.
Type
| Protocol | OpenID Connect 1.0 |
|---|---|
| HTTP method | GET |
| Type | Browser Flow |
| Endpoint | Authorization Endpoint |
| Flow Supported | Authorization code flow Implicit flow Hybrid flow |
| Response | ID Token, Access Token, Refresh Token |
| Response Mode | query, form_post, fragment |
How to configure
To Configure the authenticator, follow these steps
- Select the Settings button.
- Click Config.
Choose the actions you want to proceed with and enter the necessary configuration data. By following these steps, you will be able to successfully configure the authenticator.
Configuration
Parameters involved in Condition - Email Verification execution
| Parameter | Description |
|---|---|
| ID | Unique system UUID, which will be assigned automatically to record in a database. |
| Alias | Name for the set of configurations that occur within a specific authenticator (Example: Verify Email). |
| Authentication Flow Type | Specifies the flow in which the authenticator should be executed. |
| Check Email not verified | Enable this to verify whether the email is confirmed or not. |
User Flow
This execution contains the following main steps:
- Condition email verification must be in the conditional flow and preceded by another authenticator, as it relies on a user obtained from the previous authenticator. (Example: KOBIL Username Password Form.)