Uploaded image for project: 'Identity Gateway'
  1. Identity Gateway
  2. OPENIG-359

Introduce Audit Framework

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.1.0
    • 3.1.0
    • Core
    • None
    • Sprint 46, 3.1 - final dev sprint, 3.1 - QA sprint / bug fixing

    Description

      Extracted from a discussion with matthew:

      1. update the exchange to include client information (IP address, etc) (OPENIG-333)
      2. implement a new "audit" decorator: decorations include zero or more "scope" strings
      3. implement a new API for implementing audit consumers: consumers provide a condition expression which is evaluated in order to determine if the audit event should be routed to the consumer. The expression may check the event scopes, but could look at other aspects, like the HTTP method, IP address, etc
      4. ensure that the router adds the selected route name to the exchange so that it can be picked by the audit framework
      5. implement a simple audit consumer: a monitor endpoint. I'll leave it to you to decide what it displays, but I strongly suggest that it is CREST compatible. It could be a singleton JSON resource only supporting GET (read).

      Attachments

        Issue Links

          Activity

            People

              guillaume.sauthier Guillaume Sauthier
              guillaume.sauthier Guillaume Sauthier
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: