KOBIL QR
KOBIL QR
The main task of this execution is to authenticate the user based on scanning a QR image which is generated and displayed in the webview. QR code contains a random values, known as a nonce, which has to be scanned by the user from the mobile application (client application).
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 Actions button and select Config . The authenticator configuration screen will appear. Then enter your config data.
Note:
Required user Actions should be set to KOBIL QR. Refer User management section to know about user attribute configuration.
Configuration
Parameters involved in KOBIL QR execution
| Parameter | Description |
|---|---|
| ID | Unique system UUID, which will be assigned automatically. |
| Alias | Provide an alias name for the configuration to be set. |
| TTL of QR | Set the QR Code Timeout in Seconds. Example 20 Seconds. Defaults to 120. |
| Custom QR value | Configure the URL, with the following query param value "?qrValue={qrValue}" where {qrValue} is replaced nonce. For example 'link.com?qrValue={qrValue}'. |
| Disable Remember Me option | Enable to hide the remember me option in QR Page. |
| Disable Remain SignedIn option | Enable so that remain signedin option will not display. |
| Disable back option | Enable to display option to reset flow. |
| Enable attempted flow | Enable to skip the current authenticator/flow and countinue the next authenticator/flow. |
User Flow
Execution Flow
This execution contains following main steps:
-
A QR image is generated and displayed in the web app. QR code contains a random values, known as a nonce, which has to be scanned by the user from the mobile application (client application). If the authentication succeeds, the user is logged in.
-
The authentication will fail due to transaction timeout if the QR code is not scanned.
Note: Timeout seconds can be set by the client as per their requirement in
TTL of QRconfiguration.