Account- KOBIL Manage Devices
Account - KOBIL Manage Devices
This execution has the following main tasks
- Manage devices will return a list of actions that can be performed for the given user devices (Example: Lock, Unlock and Delete).
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.

Configuration
Parameters involved in Account - KOBIL Manage Devices execution
| Parameter | Description |
|---|---|
| ID | Unique system UUID, which will be assigned automatically. |
| Alias | Display name of configuration, which occurs in authentication flow. (Example: Manage Devices) |
| Enable Lock/Unlock Option | Enable to provide lock and unlock options. |
| Enable Delete Option | Enable to provide delete options. |
| AST Device Delete Action | Select the flow to delete the device from AST. |
| Order Devices by | Select on which order the registered device should display for the user. |
| Show Success Page | Enable to show success page in the flow. |
| Select Way of Next Step | Choose your way to continue the flow. Redirect will move to URL provided in navigation URL. Continue will move to next step. |
| Navigation URL | Provide an URL if you need any navigation option from devices page. |
| Enable Notifications | Enable to send notifications. |
| User Attribute Name for no devices | Provided attribute will be added for user when user deletes all his available devices. NOTE: This is a combination hence if provided, attribute value present below should not be null or empty. |
| User Attribute Value for no devices | Provided value will be added for user when user deletes all his available devices. NOTE: This is a combination hence if provided, attribute name present above should not be null or empty. |

User Flow
Execution Flow
This execution contains the following main steps:
- KOBIL Manage device must be preceded by another authenticator since it procures a username from this precedent authenticator. For instance: KOBIL Login for user identification.
- Based on the next step way we choose, whether
RedirectorContinuethe response will vary.
- 2a. If the next step is chosen as redirect, we will be redirected to the provided URL in configuration tab.
- 2b. If the next step is chosen as Continue, we will be redirected to move to the next step of the process.
- On successful authentication, the user device will perform the provided action (Example: Lock, Unlock and Delete).