[JIRA] (IDP-2039) Add audit logging to login flows

[Scott Cantor (Jira)]

Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) *commented* on IDP-2039 ( https://shibboleth.atlassian.net/browse/IDP-2039?atlOrigin=eyJpIjoiOTZhNjEzMDMyMjg3NGE3OWIyYzE1Nzg4Yjc2NzVlYzYiLCJwIjoiaiJ9 )

Re: Add audit logging to login flows ( https://shibboleth.atlassian.net/browse/IDP-2039?atlOrigin=eyJpIjoiOTZhNjEzMDMyMjg3NGE3OWIyYzE1Nzg4Yjc2NzVlYzYiLCJwIjoiaiJ9 )

Initial commits done adding a framework and new classes to support audit logging in any of the login flows.

Password flow was the initial POC and is logging now if a property is enabled.

Category and format will be set by property with defaults used. The logging config is not separating that OOB but contains an example for doing that.

The intent is that customizing extractors for a flow would involve defining a map bean inside the relevant flow’s config file and it’s isolated to the login flow’s context, not globally visible at root level like the rest of the auditors are. This was needed with the original logging because there was no obvious “config file” to use for that across every profile flow.

In comparison to the DuoOIDC implementation, I adjusted the log writer to allow omitting that profile logging ID suffix and I am limiting things to one format string and category rather than allowing use of a map of them.

( https://shibboleth.atlassian.net/browse/IDP-2039#add-comment?atlOrigin=eyJpIjoiOTZhNjEzMDMyMjg3NGE3OWIyYzE1Nzg4Yjc2NzVlYzYiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-2039#add-comment?atlOrigin=eyJpIjoiOTZhNjEzMDMyMjg3NGE3OWIyYzE1Nzg4Yjc2NzVlYzYiLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100211- sha1:7eca2fb )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20221206/1624e0f1/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-31475148-3e87-46ed-85af-b8cdc7d6c0b2
Type: image/png
Size: 302 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221206/1624e0f1/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-dc5b2f9e-7e5d-4c92-91b1-30aa1e849374
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221206/1624e0f1/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-d93e72c0-1e48-4e64-9595-f19b7b4ef8ce
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221206/1624e0f1/attachment-0005.png>