vigiloauth/vigilo

Add Audit logs to client management flows

Open

#363 opened on May 29, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (9 forks)auto 404
good first issuesecuritytask

Repository metrics

Stars
 (100 stars)
PR merge metrics
 (PR metrics pending)

Description

Description: We should add audit logging to all client-related flows to improve observability and traceability. This will help us monitor client actions, detect anomalies, and assist with debugging and compliance.

Tasks:

  • Identify key client flows that require audit logging
  • Add audit log entries for relevant events (e.g., login, logout, permission changes, config updates)
  • Ensure logs include useful context (user ID, timestamp, IP, action, result, etc.)
  • Update documentation if needed

Acceptance Criteria:

  • Audit logs are generated for all major client flow actions
  • Logs include enough detail to be useful for debugging and auditing
  • Logging has minimal performance impact

Contributor guide

Research direction
Review the existing client management code to identify key actions (e.g., create, update, delete clients, change permissions). Then add audit log entries at those points, ensuring to capture user ID, timestamp, IP, action, and result. Keep performance low by using async logging if needed.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60