Triggered DLP rule is not filled in for sensitive data scan.
With recent changes triggered DLP rule names are added to the reported events. This CL is mostly about make sure things are work as expected. Two changes are made: 1/ Remove extra fields from the reported rules. The server is quite strict and rejects reports if they contain bad or extra fields. This CL removes the fields 'id' and 'action' which are not handled. 2/ Rename the "result" field to "eventResult". This was an error I introduced in cl/2288811. With these changes I have verified that event reports are properly accepted by the backend. Bug: 1069109 Change-Id: Ia381da313488eee6f41d71b1ab3928c213003e43 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2308991Reviewed-by:Dominique Fauteux-Chapleau <domfc@chromium.org> Reviewed-by:
Daniel Rubery <drubery@chromium.org> Commit-Queue: Roger Tawa <rogerta@chromium.org> Cr-Commit-Position: refs/heads/master@{#790538}
Showing
Please register or sign in to comment