Details

    • Sprint:
      5.5.48-0, 10.0.24, 10.2.0-6, 10.2.0-7, 5.5.50, 10.2.2-1, 10.2.2-2, 10.2.2-3, 10.2.2-4

      Description

      A lot of desired features of the audit plugin are stalled as the current API doesn't provide necessary capabilities.
      The list of desired ones:

      • plugin data can be stored in the server table.
      • information about user's role
      • information about the tables/databases involved with the query
      • possible parser result of the query
      • export JSON functions
      • access to the information about the connection
        encryption used
        authentication method
        connection type
        connector used

      I don't think there is any reason to extend the structures that are sent to the auditing
      fucntions. The way to go is creating server functions that can be linken in the plugin - irectly or via the 'service'-s.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                holyfoot Alexey Botchkov
                Reporter:
                serg Sergei Golubchik
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: