Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-22320

Fix logging 'download' event continuously with Nuxeo Drive

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 7.10-HF25, 9.2
    • Fix Version/s: 9.2
    • Component/s: Nuxeo Drive
    • Impact type:
      API change
    • Upgrade notes:
      Hide

      Previously the 'webengine' reason was used for downloads coming from a WebEngine/Automation/REST API result.

      Now 'webengine' is used only for the subset of these that return a JSONBlob, otherwise the 'download' reason will be used.

      Downloads with 'webengine' reasons are not sent as download events by the DownloadService anymore (and therefore not logged in the audit).

      Show
      Previously the 'webengine' reason was used for downloads coming from a WebEngine/Automation/REST API result. Now 'webengine' is used only for the subset of these that return a JSONBlob, otherwise the 'download' reason will be used. Downloads with 'webengine' reasons are not sent as download events by the DownloadService anymore (and therefore not logged in the audit).
    • Sprint:
      nxFG 9.2.4
    • Story Points:
      3

      Description

      Since NXP-17234 all blob downloads are logged so Drive generates a lot of entries in the audit log for the 'download' event.
      The reason is that every time 'GetChangeSummary' is invoked a blob is returned and since this blob download is also handled by the DownloadService, a 'download' event is being notified every 30 secs => we should not notify/log this event for these downloads (when all the event properties except the name are null anyway)

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 hour
                  1h