[MGNLSSO-81] Add SSO logging to Magnolia access log Created: 03/Sep/21  Updated: 29/Sep/23  Resolved: 07/Sep/23

Status: Closed
Project: Single Sign On
Component/s: None
Affects Version/s: None
Fix Version/s: saas, 3.1.7

Type: Improvement Priority: Neutral
Reporter: Roberto Gaona Assignee: Evzen Fochr
Resolution: Fixed Votes: 0
Labels: filters, log4j2, logging
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
is duplicated by MGNLSSO-194 Audit log for Magnolia SSO module Closed
is duplicated by MGNLSSO-304 Audit Logging is not called when user... Closed
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes
Date of First Response:
Epic Link: SSO support for custom IdPs
Sprint: AdminX 43
Team: AdminX
Work Started:
Approved:
Yes

 Description   

At this moment, Magnolia's access log doesn't seem to have much use if using the SSO module. Some information could be logged into it when SSO filters are enabled to provide a better feedback to the users.



 Comments   
Comment by Jan Haderka [ 03/Sep/21 ]

How would you see that working?
In the SSO scenario, it's 3rd party to which authentication of the user is delegated, so Magnolia itself doesn't know if/when user was authenticated. It just takes for granted that when trusted 3rd party tells it user should be allowed in that user is authenticated correctly. It's the 3rd party that performs the authentication that would need to write to the access log to provide such information.

Generated at Mon Feb 12 10:50:56 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.