Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-13417

Have a public Audit Logging API accessible by plugin/custom modules/nodes.

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 13.5.1, 14.0.0, 5.5.1, 6.0.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.5.0, 6.5.0.1
    • Fix Version/s: None
    • Component/s: audit logging
    • Labels:
    • Support Ticket IDs:

      Description

      It would be good to somehow have some public API to add some extra loggable context so that when the audit are written these addition context can be logged together. Otherwise it would be good to have some more stable public server API to create new audit logging events so that customized modules, auth tree modules, PAP and other can leverage these public API to log extra information

      Category #1

      • As there is an AuditContext, maybe it would be nice if one can add to the audit context some extra JSON fields (or key value/string) that when the audit is written the these are also printed. If this is coupled with the Audit exclusion list this may help make the audit more extensible for other uses.

      Category #2:

      •  API to create one own audit logging event / category that than goes to these existing Audit logger AM has. THis will help then to create new audit entry for other purposes.

      Category #3

      • Public API to get the transactionId or context for external logging or use case.

       

       

      (Consider also if these can be created in Scripts, Trees and also in Custom modules)

       

       

       

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              chee-weng.chea C-Weng C
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: