Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Do
    • Affects Version/s: 7.0.0, 6.5.3
    • Fix Version/s: None
    • Component/s: audit logging
    • Labels:
      None

      Description

       By default we have:

      • audit logging on
      • but we do not log group and identity changes due to performance tests results problem after OPENAM-16146
      • we log access events like AM-ACCESS-OUTCOME, while same information is by default logged into the container's (tomcat) access log

      Proposal is to change default settings to have:

      • audit logging on
      • events with topic access not logged as this is usually done by container (tomcat) by default and if customer is using custom database to save logs, he will need to change configuration anyway
      • events with topic different than access logged (revert OPENAM-16146), because customers will want these things audited and will expect that our performance tests results will be with audit logging included

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                lubomir.mlich Ľubomír Mlích
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: