Skip to content
Snippets Groups Projects

Audit auditor role changes

Merged sameer shaik requested to merge auditor-audit into master
All threads resolved!

What does this MR do and why?

This MR adds an audit event at eh instance level when a user is promoted or demoted as an auditor. Currently, we log this event for and admin user and this MR logs the event for auditor role changes.

By extending the audit logging to the 'Auditor' role, we can offer instance administrators a complete and transparent view of role changes within the platform. This will enhance security, accountability, and monitoring capabilities, ensuring that any changes to roles with access to sensitive data or functionalities are adequately tracked.

Screenshots or screen recordings

Screenshot_2023-11-09_at_8.22.02_PM

How to set up and validate locally

  1. In the GDK, navigate to http://localhost:3000/admin/users/ANY_USER_NAME
  2. Edit the user and switch the role to auditor
  3. Verify the audit event in the instance level audit events page: http://localhost:3000/admin/audit_logs
  4. Switch the user back to regular user
  5. Verify the audit event in the instance level audit events page: http://localhost:3000/admin/audit_logs

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by sameer shaik

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Mario Celi added 1 commit

    added 1 commit

    Compare with previous version

  • Mario Celi resolved all threads

    resolved all threads

  • Terri Chu approved this merge request

    approved this merge request

  • Terri Chu enabled an automatic merge when the pipeline for 260633c1 succeeds

    enabled an automatic merge when the pipeline for 260633c1 succeeds

  • merged

  • @terrichu, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline was created more than 4 hours ago, you should:

    1. Ensure the merge request is not in Draft status.
    2. Start a pipeline (especially important for Community contribution merge requests).
    3. Set the merge request to auto-merge.

    This is a guideline, not a rule. Please consider replying to this comment for transparency.

    This message was generated automatically. You're welcome to improve it.

  • sameer shaik mentioned in commit 1cde5e88

    mentioned in commit 1cde5e88

  • Terri Chu mentioned in commit 10d973e9

    mentioned in commit 10d973e9

  • removed documentation label

  • added workflowstaging label and removed workflowcanary label

  • mentioned in issue #430235 (closed)

  • Please register or sign in to reply
    Loading