Launchpad itself

Appserver access log should contain username

Bug #341936 reported by Herb McNew
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Currently there is no way to correlate an action with a particular user. We'd like to have the app server record the username in either the ident or username field of the access log.

Revision history for this message
Diogo Matsubara (matsubara) wrote :

Hi Herb,

you mean a log like devpad:/srv/launchpad.net-logs/edge/gangotri/launchpad-access1.log ? If yes, I think 12nd field is the DB id. Does that help or you need it to be the username? Can you explain the use case for having the username there?

Thanks

affects: launchpad → launchpad-foundations
Changed in launchpad-foundations:
status: New → Incomplete
Revision history for this message
Herb McNew (herb) wrote :

Diogo,

It does, in fact, look like the DB id. I think we'd much rather see the LP username in that field though. This is primarily for auditing purposes. Because we don't have any sort of audit log we have to go through the logs to correlate information. Having the username as opposed to the DB id would make that a bit easier on us.

A better solution all around might be some sort of audit log. Maybe something like "<date> User <x> added bug <y> from IP <z>" or "<date>: User <x> changed his password from IP <z>." This sort of thing would be beneficial in several situations. For example, blocking spammers or tracking account compromises.

Regards,
Herb

Diogo Matsubara (matsubara)
Changed in launchpad-foundations:
status: Incomplete → Triaged
importance: Undecided → Low
Tom Haddon (mthaddon)
tags: added: canonical-losa-lp
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.