#5514 - Add a unit test for removal_default_handle_method and allowed_handle_methods in privacy hooks
-
By PDStig
- Added
- 9 views
| Identifier | #5514 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Add a unit test for removal_default_handle_method and allowed_handle_methods in privacy hooks |
| Status | Completed |
| Tags |
Roadmap: v11 (custom) Type: Legal compliance / Privacy (custom) |
| Handling member | PDStig |
| Addon | General / Uncategorised |
| Description | If a unit test does not already exist, add a unit test that makes special considerations for removal_default_handle_method and allowed_handle_methods.
If the privacy hook's removal_default_handle_method is delete, the test should fail for the hook (and suggest using anonymise instead) if any of these conditions are true: * There are multiple member_id_fields defined // We don't want to delete records that could still be associated with other members * There are multiple ip_address_fields defined // We don't want to delete records that could still be associated with other devices * There are multiple email_fields defined // We don't want to delete records that could still be associated with other members / e-mails allowed_handle_methods should also fail if it allows the delete action and any of the above conditions are true. |
| Steps to reproduce | |
| Related to | #5513 - Auto-delete certain data when an account is deleted #5512 - Secondary Privacy block detailing the data stored in the database |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments