User PII Cleanup

Overview

The user deletion requirement in inQuiry has been originated from the below requirement.

PRD: [PRD] Delete Account functionality

BE Design Lern - [Design] Delete Account Functionality

FE Design Lern - [Design] [Front-end]Delete User Functionality

What is changing?

The user can request for deletion of their account in Sunbird, this means two primary actions to happen.

1. User's Personal Identifiable Information (PII) needs to be removed

2. The assets (like questions, questionSets, content etc) that was created by this user needs to be transferred to an identified user.

Changes for Learn:

1. Learn BB provided user delete api which produces a kafka event on <env>.delete.user topic.

2. For more details on the delete user api, please visit

Changes for inQuiry:

1. PII data cleanup feature released under inQuiry 7.0.0 release.

2. inQuiry provided a flink job user-pii-data-updater for user PII data cleanup activity.

3. The flink job listen to <env>.delete.user kafka topic and process the data accordingly.

4. The job works for all object type (including Question, QuestionSet, Content, Collection, Assets) which are configured to the job.

5. The flink job will search for all the objects (configured with flink job) owned by deleted user and update the pii field configured under object schema(e.g: creator) to the pre-configured value (e.g: Deleted User / Anonymous user) with the flink job.

6. PII field configuration is part of each object schema (config.json) because there could be different pii field for each object.

7. Sample PII Config is as below:

   Ref: https://github.com/Sunbird-inQuiry/inquiry-api-service/blob/a0352eb2dfa6ccc4433dc15c44610db286deb12e/schemas/question/1.0/config.json#L58

   "PII_Fields": { "user": { "createdBy": ["creator"] }, "org": { } }

8. The job triggers a notification email to the org admin with all identifiers affected for Deleted user.

Release Tags:

Component	Service to be Build	Build Tag	Deploy Job	Deployment Tag	Comment
InquiryUploadSchema	NA	NA	Deploy/Kubernetes/UploadSchema	release-7.0.0_RC4	schema tag: release-7.0.0_RC4 Note: the job should be re-imported using script
InquiryKafkaSetup	NA	NA	Deploy/job/dev/job/KnowledgePlatform/job/InquiryKafkaSetup/	release-7.0.0_RC4	A new kafka topic <env>.delete.user has to be created for user-pii-data-updater flink job
InQuiryFlink Job	Build/job/KnowledgePlatform/job/InquiryFlinkJob	release-7.0.0_RC7	Deploy/job/dev/job/KnowledgePlatform/job/InquiryFlinkJob/	release-7.0.0_RC7	A New Flink Job user-pii-data-updater is added. Config File Reference For Above Job: https://github.com/Sunbird-inQuiry/data-pipeline/blob/2297fe1288654283f586d1802d458f4238c1e3f6/kubernetes/helm_charts/datapipeline_jobs/values.j2#L264

Variables Added to user-pii-data-updater flink job for PII Cleanup Use case:

Variable Name	Description	Default Value
user_pii_updater_kafka_topic_name	Input Kafka Topic Name	{{ env_name }}.delete.user
user_pii_updater_group	Group Name For The Flink Job	{{ env_name }}-user-pii-updater-group
user_pii_target_object_types	Target Object Type and Schema Version should be configured as value . e.g: If you want to process 5 different objects for deleted user, then all 5 object types should be part of this configuration along with corresponding schema versions.	'{ "Question": ["1.0", "1.1"], "QuestionSet": ["1.0", "1.1"] }'
user_pii_replacement_value	The value which need to be inserted for target pii fields.	"Deleted User"
admin_email_notification_enable	This falg is used to enable/disable email notification for admin	true
user_org_service_base_url	Base Url of userorg service for sending notification	"http://{{private_ingressgateway_ip}}/userorg"
email_notification_subject	Subject Line for Email Notification	"User Account Deletion Notification"
email_notification_regards	Value For Regards in Email Notification	"Team"