[Design] Delete Account Functionality
Introduction
This wiki explains the design for delete user account feature. As of now there is no hard delete of user profile flow available in Sunbird. At present, we have functionality to BLOCK/UNBLOCK users.
Background & Problem Statement
Sunbird supports the mobile app for Android and iOS. As per the latest policy update of the Apple App Store and Google Play Store, mandates the user deletion from the app, if the app is having the signup from app. The specific policy mandates can be found using the following links:
Apple App Store Policy - https://developer.apple.com/app-store/review/guidelines/#data-collection-and-storage
Apple App Store Policy - https://developer.apple.com/support/offering-account-deletion-in-your-app
Google Play Store Policy - https://support.google.com/googleplay/android-developer/answer/13327111?hl=en
Registered users must have access to a "Delete Account" option on both the app and the portal. This option will allow them to initiate the account deletion process themselves.
Key Design Problems
User should not able to do the following things after successful deletion of account:
User should not be able to login by using the existing login credentials post account deletion.
Any of the Personally Identifiable Information (PII) of the user, such as name, email, and phone number should not be available in any DB in any format (even encrypted format).
Other than PII data should not be deleted. User transactional data and user created contents (usage, rating etc) are to be retained.
Certificates issued to the deleted users should not be accessible, but should be verifiable. (Storing only the name of the user in Sunbird RC to display in certificate).
External id of the SSO user should be removed.
List the deleted user list to admin dashboard.
Deleted user’s asset should be transferred to the other user after successful deletion.
Design
Delete User
Send the OTP to the user’s email/phone to validate the user. (OTP templates for user account deletion verification)
Sync
Delete login credentials and sessions from Keycloak.
Update the
sunbird.usertable. Set the following fields as empty: (redis data for the following fields will become empty for that user)firstName
lastName
email
dob
phone
maskedEmail
maskedPhone
prevUsedEmail
prevUsedPhone
recoveryEmail
recoveryPhone
Update the status from ACTIVE to DELETED.
Remove the user entry from
sunbird.user_lookuptable.Remove the SSO user entry from
sunbird.user_external_identity.Send the AUDIT telemetry event after successful/failure update/deletion of the above tables.
Trigger the delete user kafka event
{{env_name}}.delete.user
User Deletion Flink Job
Verify the sync steps is successfully completed else perform the pending actions.
Update the user entry in
sunbird.user_organisation(async) - May not be required.isdeleted - True
orgleftdate - system date
Update the user’s name in nodeBB as Deleted User to display in discussion forum.
Group - TBD
Send the AUDIT telemetry event after successful/failure update/deletion of the above tables.
User delete API:
Delete User Kafka Event
Property | Description |
|---|---|
organisationId | It helps to identify user belongs to which organisation |
userId | Deleted user id |
suggested_user | If user have role other than PUBLIC, than suggested user list can be send in the event for each role user is having. |
Deleted Users search curl
User search API can be used to get the more detail about user. e.g. name.
OTP Template
SMS
Backward compatibility Approach:
As part of backward compatibility, ‘User Deletion Flink Job’ mentioned above can be deployed; ‘delete-user’ kafka topic can be created and events to the kafka topic can be inserted via scripts by passing users' information as part of the topic for completing user deletion activity.
Manage Learn -
As part of the Manage Learn use case, the user’s PII data is captured and/or used in the below-mentioned workflows -
A complete snapshot of a user’s profile which includes name (first and last name) as well as masked email and phone is captured under various collections in MongoDB (observations, projects, survey, and programUsers) at the start of any transaction i.e. the moment a user starts working on a survey, or project or decides to join a program. This is done to give the Program manager the details of the user as it was when he/she started working on the resource and is not affected by his/her profile change later. This means a user’s name, location, role, and sub roles which is later used for certificate generation using Sunbird RC is the same when he/she started the resource.
When the Program Manager requests reports via the Program Dashboard about the details of each and every user who has worked on a resource or has joined the program, the user’s email and phone along with the name is provided via a CSV using the Lern Data Product. These details are fetched in real-time at the moment of generating the on-demand report from the common and shared Redis and Cassandra storage. No change is required here since the expectation is user’s name, email phone will be deleted from the common storage and replaced with the “Deleted User” string, We will just need to test this once to confirm the entry from the reports is not removed but just the PII data is removed.
Note - No other place in Logs, Druid, ES or Neo4j does Manage Learn workflow write to
As part of the user delete flow we plan to implement the following changes in the Mangage Learn side:-
Build a Kafka consumer in each micro-service (Survey, Projects, and ML Core) to listen to Kafka events on topic - TBD Point 4 which will do the following thing.
Check if any transactions are recorded for this user and if yes, remove all user name, email, and phone entries based on the userId from all collections i.e. projects, surveySubmissions, observations, observationSubmissions, and programUsers of MongoDB.
Update the status via API in
sunbird.user_deletion_statustable. Refer - TBD Point 2
Build a Kafka consumer in each micro-service (Survey, Projects, and ML Core) to listen to Kafka events on topic - {{envName}}.tranfer.ownership.job.request which will do the following thing.
Check if any assets are owned by the deleted user and that the new owner has required platform roles (i.e. Program Manager or Program Designer), if yes update the owner/author in the collections i.e. programs, solutions of MongoDB.
Update the status via API in
sunbird.user_ownership_transfertable. Refer - TBD Point 3
NOTE: None of the services should log the user PII data.
References
Apple App Store -
Google Play Store -