Following T271270: Create new logging table in SecurePoll, log when admins access voter data.
This task is only for adding a row to the log table.
Details of how we could do this are outlined in T270342#6702969.
Tchanders | |
Jan 5 2021, 10:07 PM |
F34099640: log_list.png | |
Feb 10 2021, 3:44 PM |
Following T271270: Create new logging table in SecurePoll, log when admins access voter data.
This task is only for adding a row to the log table.
Details of how we could do this are outlined in T270342#6702969.
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Log when admins access voter data | mediawiki/extensions/SecurePoll | master | +17 -0 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | jrbs | T152972 Accessing private information through SecurePoll should be logged | |||
Resolved | STran | T271276 Log when admins access voter data in SecurePoll |
Dependent on T271270: Create new logging table in SecurePoll; stubbing this out in the meanwhile
Change 655545 had a related patch set uploaded (by STran; owner: STran):
[mediawiki/extensions/SecurePoll@master] [WIP] Log when admins access voter data
Change 655545 merged by jenkins-bot:
[mediawiki/extensions/SecurePoll@master] Log when admins access voter data
We now record every time an admin goes to Special:SecurePoll/list/<id>. A log entry is also recorded every time you refresh or use pagination. So you may see lots of entries for the same user and election (like below).
A log entry is only recorded if the user is an admin of the election and is in the electionadmin group. If a non-admin user goes to /list, they do not see any of the personal data (e.g. IP, UA) and a log entry is not recorded.
Test environment: local vagrant SecurePoll 2.0.0 (1ebc4fd).