KOBIL Change Email
KOBIL Change Email
The main task of this execution is to change the Email ID of the User.
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 access the config of the execution press the Settings button and select Config. The authenticator configuration screen will appear. Then enter your config data.
Configuration
Parameters involved in KOBIL Change Email 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 (e.g., Registration Flow). |
| Authentication Flow Type | Type of flow for which the authenticator is used. (Example: Registration) |
| User Identity attribute | User property to identify the user for login validation. Default : Email. |
| Display User Identity Attribute | User property to be displayed for login validation. |
| User Attribute | User attribute value selected for login validation. This should be set only if the User Identity Attribute value is "user attribute" |
| Enable Password Check | If enabled, Password verification process will be executed. |
| Invalid User ID message | Message to be displayed when the user ID is invalid or user not found. |
| Invalid credentials message | Message to be displayed when the user credentials invalid. For default invalid username or password. |
| User disabled message | Message to be displayed when the user is disabled. Default Message: User is currently disabled, please contact admin. |
| ACR value | This ACR value will be set in the end, if verification succeeds |
| AMR value | This AMR value will be set in the end, if verification succeeds |
| Show Success Popup Screen | Enable to show success popup in the flow. |
| Success Popup Title | Text wil be displayed in the success popup title. |
| Success Popup Description | Text wil be displayed in the success popup body. |
| Email Verification Code Length | Length of the Email Verification code. The default value is 6. |
| Email Verification type | Email to be verified by OTP or link. Default is OTP. |
| Email Verification Code TTL | Provide the validity of the verification code. (Example: for days 2d, for hours 2h, for secs 2s.) Default value is 1h. |
| Email OTP Expired Message | Message to be displayed when the user enters expired OTP. |
| Email Verified Message | Message to be displayed when the Email is verified. |
| Show Email Confirmation | Enable to show email confirmation view. |
| JSON Script | JSON to display inputs in Headless V2 theme. |
Parameter specific to Brute force feature
| Parameter | Description |
|---|---|
| Retry Attempt Exceeded | To display the retry exceeded message along with the timer. |
| User temporarily locked message | Message to be displayed when the user is temporarily locked. Example: User is temporarily locked for %time% minutes. |
| Reset Bruteforce failure count | If enabled the Bruteforce failure count will be set to 0 on successful login. |
Parameter specific to Resend OTP Bruteforce feature
| Parameter | Description |
|---|---|
| Reset OTP Bruteforce failure count | Enable to reset OTP Brute Force failure count on successful login. It is disabled by default. |
| REG Enable Session OTP brute force | Enable the Session OTP brute force. Enabled only for the Registration flow. |
| REG Max Session OTP Resend | Number of re-tries a user is allowed to do. (Example: 10, Default: 5). Used only in the Registration flow. |
| REG Wait Increment | Wait time (in seconds) for the user, if the user gets locked. (Example: 3600, Default: 5). Value has to be in seconds. |
| Resend Interval Duration | Enter the duration for for Resend code interval. |
User Flow
Execution Flow
This execution contains the following main steps:
- KOBIL Change Email must be preceded by another authenticator since it procures a user from this precedent Authenticator. For instance: KOBIL Configure User Identity for user identification.
- User will provide email ID and password, If the email is not registered with any user, the password will be validated.
- Once the password validation succeeds , OTP will be sent to the mail. If the OTP is verified, the user will be verified with email.