Currently when a consent purpose is created and a consent is taken from a user (consent record is created), the related consent purpose cannot be deleted or modified. This leads to a blocker situation in deleting any of the resources as we cannot delete consent records. Even revoking the consent will not allow the purpose to be deleted.
- Consent purpose cannot be deleted/ modified due to associated consent record
- Consent elements cannot be deleted due to associated consent purpose
Also as per an offline chat, noted that consent record stored here is not for the auditing purposes. Auditing will have a separate immutable record. If that's the case, is there an issue allowing to delete the consent record?
Note: Consent record deletion/ revocation should happen automatically when deleting the consent purpose. It's not ideal to send burst delete request for each consent from the caller service
Requirement:
In thunder, we are creating a consent element for each user attribute and a consent purpose for each application when configuring user attributes for it. After taking the consent from a user, if the application developer wants to edit the shared attributes (remove already shared ones/ add new ones), we should be able to update the existing consent purpose or create a new version of it.
Currently when a consent purpose is created and a consent is taken from a user (consent record is created), the related consent purpose cannot be deleted or modified. This leads to a blocker situation in deleting any of the resources as we cannot delete consent records. Even revoking the consent will not allow the purpose to be deleted.
Also as per an offline chat, noted that consent record stored here is not for the auditing purposes. Auditing will have a separate immutable record. If that's the case, is there an issue allowing to delete the consent record?
Note: Consent record deletion/ revocation should happen automatically when deleting the consent purpose. It's not ideal to send burst delete request for each consent from the caller service
Requirement:
In thunder, we are creating a consent element for each user attribute and a consent purpose for each application when configuring user attributes for it. After taking the consent from a user, if the application developer wants to edit the shared attributes (remove already shared ones/ add new ones), we should be able to update the existing consent purpose or create a new version of it.