[MAGNOLIA-6286] auditLogging doesn't log login events Created: 07/Jul/15  Updated: 05/Aug/15  Resolved: 28/Jul/15

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.3.6, 5.4
Fix Version/s: 5.3.11, 5.4.1

Type: Bug Priority: Major
Reporter: Zdenek Skodik Assignee: Christoph Meier
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: 0d
Time Spent: 0.75d
Original Estimate: Not Specified

Issue Links:
Relates
causality
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Sprint 3 (Vietnam), Sprint 4 (Basel)
Story Points: 5

 Description   

Apparently introduced by MAGNOLIA-5991.



 Comments   
Comment by Christoph Meier [ 28/Jul/15 ]

Introduction of LoginResult.STATUS_SUCCEEDED_REDIRECT_REQUIRED was the reason that logging of the login and logout events wasn't logged anymore.

Beside that,
to make sure to have login and logout events logged at magnolia-audit.log, the properties
/server/auditLogging/logConfigurations/login@logName
/server/auditLogging/logConfigurations/logout@logName
must be set accordingly.
By default the name property for these 2 attributes are set to log-access.
In order to have login / logout logged at magnolia-audit.log, name properties must be set to log-audit.

Comment by Christoph Meier [ 28/Jul/15 ]

Fix is on branch MAGNOLIA-6286 (see https://git.magnolia-cms.com/gitweb/?p=magnolia_main.git;a=shortlog;h=refs/heads/MAGNOLIA-6286)

Generated at Mon Feb 12 04:13:04 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.