Record audit event when user is blocked
What does this MR do?
Record audit event when the user is blocked.
A user can be blocked via a number ways:
- Admin interface (https://docs.gitlab.com/ee/user/admin_area/blocking_unblocking_users.html#blocking-a-user)
- Abuse report (https://docs.gitlab.com/ee/user/admin_area/abuse_reports.html#blocking-users)
- API (https://docs.gitlab.com/ee/api/users.html#block-user)
This MR only covers the first method as the other two invoke blocking logic directly on user (i.e. user.block), rather than utilising a service object. We will prioritise effort to bring audit event log to the other methods at later stage.
See parent issue #251 (closed)
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers - [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec - [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team
Edited by Tan Le