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

Audit Event Handler ignores realm-based log configurations

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 13.0.0, 13.5.0
    • Fix Version/s: 13.5.1, 14.0.0
    • Component/s: audit logging
    • Labels:
    • Support Ticket IDs:

      Description

      JDBC Audit Event Handler ignores realm-based log configurations.

      Steps to reproduce:

      1. Create three realms (realm1/realm2/realm3).
      2. Createt MySQL schemas (audit/audit1/audit2) for audit events.
      3. Createt Audit Event Handlers:
        global: JDBC Database URL: jdbc:mysql://localhost:3306/audit
        realm1: JDBC Database URL: jdbc:mysql://localhost:3306/audit1
        realm2: JDBC Database URL: jdbc:mysql://localhost:3306/audit2
      4. Restart OpenAM server.
      5. Access and Login to OpenAM server with query string "?realm=realm1".
        -> Access audit logs are inserted in "audit" schema.
        The same is true of other realms.

      The admin-guide describes:

      Global and Realm-Based Log Configuration. You can configure audit logging globally, which ensures that all realms inherit your global log settings. You can also configure audit logging by realm, which allows you to set different log settings for each realm.

      https://backstage.forgerock.com/#!/docs/openam/13/admin-guide#chap-audit-logging

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                andrew.dunn Andrew Dunn [X] (Inactive)
                Reporter:
                kohei kohei
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: