-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Right to be forgotten for users #2672
Labels
DPIA
P0: Critical path blocker
Blocking testing or the launch critical path, drop everything to investigate & fix
Milestone
Comments
Will start by adding a delete user button to the admin console page. I don’t think sources have associated users, for cases it will be trickier as it would potentially mean updating millions of cases (in theory, in practice, there are no user uploads to G.h at the moment), so we could keep a one-off script for that. |
iamleeg
added a commit
that referenced
this issue
May 24, 2022
At some point, the Google OAuth provider has changed from not returning a name at all (i.e. undefined) to returning null for a name. Because this can be stored in the database, it produces 500 errors when viewing the user table (even though the curator UI could correctly handle any falsey value for the name). This change documents that the name is nullable, allowing the null to be passed through and correctly interpreted by the UI.
iamleeg
added a commit
that referenced
this issue
May 25, 2022
iamleeg
added a commit
that referenced
this issue
May 25, 2022
iamleeg
added a commit
that referenced
this issue
May 25, 2022
iamleeg
added a commit
that referenced
this issue
May 25, 2022
The register endpoint logs in the created user, so the last created must be an admin for delete to work.
iamleeg
added a commit
that referenced
this issue
May 25, 2022
iamleeg
added a commit
that referenced
this issue
May 25, 2022
The register endpoint logs in the created user, so the last created must be an admin for delete to work.
iamleeg
added a commit
that referenced
this issue
May 25, 2022
At some point, the Google OAuth provider has changed from not returning a name at all (i.e. undefined) to returning null for a name. Because this can be stored in the database, it produces 500 errors when viewing the user table (even though the curator UI could correctly handle any falsey value for the name). This change documents that the name is nullable, allowing the null to be passed through and correctly interpreted by the UI.
iamleeg
added a commit
that referenced
this issue
May 25, 2022
iamleeg
added a commit
that referenced
this issue
May 25, 2022
iamleeg
added a commit
that referenced
this issue
May 25, 2022
iamleeg
added a commit
that referenced
this issue
May 26, 2022
At some point, the Google OAuth provider has changed from not returning a name at all (i.e. undefined) to returning null for a name. Because this can be stored in the database, it produces 500 errors when viewing the user table (even though the curator UI could correctly handle any falsey value for the name). This change documents that the name is nullable, allowing the null to be passed through and correctly interpreted by the UI.
iamleeg
added a commit
that referenced
this issue
May 26, 2022
iamleeg
added a commit
that referenced
this issue
May 26, 2022
iamleeg
added a commit
that referenced
this issue
May 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
DPIA
P0: Critical path blocker
Blocking testing or the launch critical path, drop everything to investigate & fix
If someone wants their personal information removed, we should be able to do so within 30 days of the request. I suggest we have something like the stackoverflow "Community User" to take over ownership of any sources, uploads etc. associated with deleted users.
The text was updated successfully, but these errors were encountered: