Consent management refers to the practice of prompting, collecting, and managing user approval for collecting or sharing the user's personal information. "Consent" itself is granting permission or agreement for a specified action to take place. This page guides you through consent management concepts and how they are supported in WSO2 Identity Server.
...
A consent should be freely given and should offer a genuine choice.
A consent should be specific about its purpose.
A consent should be clearly informed, and the processing organization should ensure that the subject understands what exactly is being shared and for what purpose, especially children.
A consent should be given by a statement or by a clear affirmative action such as through an electronic form submission.
Consent management with WSO2 Identity Server
WSO2 IS provides a comprehansive consent management solution that can be used to manage consents related to Identity and Access Management (IAM) and also to manage consents that belong to third party applications. The WSO2 IS consent management module consists of the following key features.
- RESTful consent APIs to manage consents remotely. For more infomation, see Using the Consent Management REST APIs.
- Consent portal for individuals to review, modify, and revoke already given consents. For more information, see Configuring consent for services.
- Admin portal support for organizations to define and manage consent, data processing purposes, and user attributes per consent. For more information, see Managing Consent Purposes.
- Consent collection during single sign-on (SSO) before sharing the user attributes with external applications. For more information, see Consent Management with Single-Sign-On.
- Support for the Kantara consent receipt specification. For more information, see the Kantara Consent Receipt Specification.
Consent management usecases
| Table of Contents | ||||
|---|---|---|---|---|
|
Handling consent when creating a new user profile
According to most privacy standards, it is mandatory to inform individuals about the purpose of processing personal data and to state what kind of data will be shared in a clear and transparent manner at the time of data collection. Furthermore, the processing organizations should get active consent from an individual for each of the data processing purposes before data collection takes place. The following points give a high level description of how this usecase is supported in WSO2 IS.
The identity administrator of an organization can define personal data processing purposes and a list of user attributes used for each of the processing purposes via admin console or via the consent REST API.
During the sef sign-up process, the data processing purposes (reason for collecting consent) along with the user attributes for each purpose will be shown to users as consents. The users can selectively opt-in/opt-out on each of the purposes.
Users can review or revoke already given consent by logging in to WSO2 IS end user dashboard (self-care portal).
Personal data processing applications can check for consent for each user through the consent REST API before carrying out any data processing activities.
| Tip |
|---|
For more information and instructions for setting up this use case, see Consent Management for Self Sign Up. |
Handling consent when sharing user attributes
According to privacy best practices and privacy standards, sharing user attributes to external parties should be based on clear and active consent (unless there is clear legal background support for information sharing). WSO2 IS shares user attributes with other applications in the form of security tokens such as SAML2 , OpenID Connect IDToken, or JWT and all of this user information sharing is based on consent. The following points give a high level description of how this usecase is supported in WSO2 IS.
The identity administrator of an organization can define purposes and user attributes for each purpose on a service provider (SP) basis using the WSO2 IS admin console or via WSO2 remote APIs.
When sharing the user attributes during flows such as SAML SSO and OpenID Connect SSO, WSO2 IS prompts the consent screen for users. The sharing of user attributes through security tokens is based on the consent that the user approves at this point.
Users can review or revoke already given consent by logging in to the WSO2 IS end user dashboard (self-care portal).
| Tip |
|---|
For more information and instructions for setting up this use case, see Consent Management with Single-Sign-On. |
Manage consents that belong to third party applications
WSO2 IS can be used to manage consents that belong to third party applications and services. To do this, third party applications can integrate with WSO2 IS using the consent REST APIs and other admin APIs provided by WSO2 IS. Note that generating and handling consent UIs for third party applications can not be supported in WSO2 IS as it is considered the responsibility of the relevant third party application to provide consent management UI facilities for their end users.
| Tip |
|---|
| For more information and instructions for setting up this use case, see Using the Consent Management REST APIs. |
Support for Kantara consent receipt (draft) specification
A consent receipt is a representation of the consent provided by a person at the point he/she agrees they agree to share the personal information with an external party. WSO2 IS consent REST APIs support the specification provided in the Kanatara consent receipt 1.1.0 (7th draft) version. For more information, see the Kantara Consent Receipt Specification.
| Tip |
|---|
For more information and instructions for setting up this use case, see Using the Consent Management REST APIs. |