KOBIL Consent Manager
KOBIL Consent Manager
Main task of this execution is to gather and maintain user consent for processing their personal information.
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 KOBIL Login execution
| Parameter | Description |
|---|---|
| ID | Unique system UUID, which will be assigned automatically. |
| Alias | Display name of configuration, which occurs in authentication flow. (Example: Demo) |
| Consent Scope | Defines the consent's scope, whether local, global, or none. Note: If the script accepts consent from one client, it will accept consent from all clients. When the consent is defined in the IAM client scopes rather than the script, pick none. |
| Version | Set the version number for consents. |
| Content | Set content that needs to be displayed to the user in order to accept the consents. |
| Client Scopes | Add script for consent management scopes. Note:Name should be unique for each consent. |
User Flow
Execution Flow
- KOBIL Consent Manager must be preceded by another authenticator, since it procures username from this precedent authenticator. For instance: KOBIL Username Password Form for user identification.
- The authenticator will collect and maintain user consent for processing their personal information.