![[ DNS Administrator ]](/fx/dnsadmin-logo.png){kind=logo}
Custom Query (15 matches)
Results (7 - 9 of 15)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #35 | fixed | Shuffle all action logging into DNSDB.pm | ||
| Description |
Current logging practice is mostly separate calls from the UI layer, using a UI-local sub that directly accesses the database (problem: SQL in the UI, see #1). For consistency and reduced code bulk/duplication in the UI layer, logging should be moved to the internals of each sub. This requires that userdata be more conveniently accessible in DNSDB.pm. |
|||
| #33 | fixed | Create "shadow users" for RPC calls | ||
| Description |
Mainly for logging consistency; for future log-viewing pleasures we need a way to sort and filter log entries based on username, user ID, user fullname, etc, etc. RPC users will likely not be native users, and so will (initially) lack a user ID. To work around this, create a new class of user (not displayed in the user lists?) to give these remote users an entry in the local user table for log processing. |
|||
| #32 | duplicate | Security review - Access scoping | ||
| Description |
Check to make sure a user can't access any entity outside of their group tree |
|||
