Bug 534187 (RHQ-1007)

Summary: RFE: provide audit log of which users logged in and when.
Product: [Other] RHQ Project Reporter: John Mazzitelli <mazz>
Component: Core ServerAssignee: RHQ Project Maintainer <rhq-maint>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: unspecifiedCC: jshaughn, lakagwu, mshirley
Target Milestone: ---Keywords: FutureFeature, SubTask
Target Release: ---   
Hardware: All   
OS: All   
URL: http://jira.rhq-project.org/browse/RHQ-1007
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 534205    

Description John Mazzitelli 2008-10-22 09:37:00 EDT
It would be nice if RHQ stored some login audit trail information, such as who logged in and when they logged in.

Would need a page (probably in Administration somewhere) that lets you view this login audit trail and purge old audit data you no longer need.

Would need new code in DataPurgeJob to purge the audit trail to avoid it growing unbounded.
Comment 1 John Mazzitelli 2008-10-22 09:41:44 EDT
The db table needed would be very simple - since its a log purely for security-auditng purposes, you don't need any foreign key relationships back to the subject table.  Just store the username and the login time.  Then we can run simple reports on that two-column table such as "who logged in in the last month", "how often did joey log in in the past year", etc.

TABLE: rhq_login_audit
COLUMNS: subject (VARCHAR), login_time (LONG)
Comment 2 Red Hat Bugzilla 2009-11-10 15:21:45 EST
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1007
Comment 3 wes hayutin 2010-02-16 10:49:54 EST
mass move off of the qa rhq_triage queue, these are dev subtasks
Comment 4 Corey Welton 2010-08-18 11:41:18 EDT
*** Bug 534205 has been marked as a duplicate of this bug. ***