`ログ匿名化の詳細`設定でユーザー名が完全に匿名化されない

zogstrip · 2026 年 1 月 1 日午後 12:52

ユーザー名に基づいて何かを削除するのは少々厄介で危険なので、代わりにコンテキストと詳細フィールド全体を [ユーザー匿名化のため削除されました] というメッセージに置き換えることにしました。

github.com/discourse/discourse

FIX: Clean up historical staff logs when anonymizing users

main ← fix-anonymizer-historical-logs

opened 12:50PM - 01 Jan 26 UTC

ZogStriP

+47 -0

When `log_anonymizer_details` is disabled, the anonymization process correctly a…voids recording the old username in the new "anonymize_user" log entry. However, historical staff action logs created before anonymization (like "check_email") could still contain the original username in fields like `context` or `previous_value`, making it possible to link an anonymized user back to their original identity. For example, when an admin views a user's email from `/admin/users/123/johndoe`, the staff action log stores that URL path in the `context` field. After anonymization, this path still contains "johndoe", defeating the purpose of the setting. This fix passes the original username to the AnonymizeUser background job, which now scrubs any historical UserHistory records that contain the username. Rather than attempting error-prone string replacement, affected fields are replaced with "[removed due to user anonymization]" to make it clear why the data is missing while preserving the audit trail. Ref - https://meta.discourse.org/t/387500

トピック		返信	表示
User anonymization and staff_action_logs Support	7	704	2021 年 9 月 8 日
User still able to log in after anonymization Bug anonymization	4	69	2025 年 11 月 30 日
Username change logging even if it failed Bug	3	589	2019 年 5 月 13 日
Profile links not updated after anonymizing an user? Support anonymization	0	122	2021 年 7 月 5 日
Admins changing user's name (not username) should be logged Bug	5	746	2018 年 11 月 22 日

`ログ匿名化の詳細`設定でユーザー名が完全に匿名化されない

関連トピック