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
[pretix as OpenIDConnect client OIDC] Customer Account Anonymization does not delete their unique identifiers #3921
Comments
Hmm, yes, this is not good the way it is. Changing the identifier, however, is also not good. Will need to think about this - currently I'm not sure why we went with hashed uids in the first place, there was some reason but I can't remember it currently. |
From privacy aspects (not my current problem of being unable to log-in as myself, what is the case at the moment - I have to try to change my "old", still blocking "sub" in the database), an anonymising operation should clean up also the It' s not visible any longer, but present (somewhere under the hood). |
In my view, when email address and name are deleted as appears to be the case at the moment, I am interested to learn, why the unique reference (sub aka Referenz) is not - this In my view, it is the most "evil" item of all the sso data - which need to be deleted in any case when "anonymisung". Pretix still has its own Kundennummer, that's fine enough to "bind" the bookings to that person. As mentioned: I am interested to learn and to understand, why the identifier is still present and, my problem, blocking. If and only if the blocking is the important part, for example to avoid impersonication, that would be probably valid reason. I would like to learn, why exactly (case study). |
The |
Ok. But in that way it still prevents me from creating a new account via my credentials from that provider. As I am a MySQL/MariaDB person: could you be so kind to post here the Postgresql code to delete that specific entry manually? |
Dear @raphaelm , if you prefer to close my issue report: it will be fine for me. One solution as proposed: during anonymization: add
|
[UPDATE]
A workaround (manual renaming of the inactive pretix-internal
identifier
toidentifier.OLD
) is described below #3921 (comment) YMMV.Problem and impact
tl;dr
Bug: Customer Account Anonymization does not delete their unique identifier.
Long version:
Problem:
As Admin, I wanted to delete my Customer Account, but there is not function to delete, only a function to "anonymize" an account, what I did.
Expected behaviour
The expected behaviour is:
That anonymization also(!) anonymizes the unique indentifier (here from SSO "sub") in order to allow a fully new user account creation.
But this was apparently not the case!
A new SSO Login - I expected a NEW customer account to be created - failed surprisingly with the message:
tl;dr
Bug: Customer Account Anonymization does not delete their unique identifier.
Steps to reproduce
See above
Screenshots
Link
No response
Browser (software, desktop or mobile?) and version
No response
Operating system, dependency versions
No response
Version
2024.1.0
The text was updated successfully, but these errors were encountered: