vigiloauth/vigilo

Add admin protected routes for client management

Open

#364 opened on May 29, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (9 forks)auto 404
admin-uifeaturegood first issuepriority: medium

Repository metrics

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

Description

The Admin UI will need new endpoints to meet some of the requirements. Below is a list of them that are ready to be implemented.

Notes:

If you choose to implement one, please create a new issue and add this as the parent issue. You also have free range to refactor or create new files if you believe it is necessary.

Documentation for the new endpoints would also need to be added.

Related files:

  • middleware.go
  • routes.go
  • roles.go

Endpoints:

  • GET /admin/clients — List all clients
  • GET /admin/clients/:client_id — Get client details
  • POST /admin/clients — Register a new client (static)
  • PUT /admin/clients/:client_id — Update client details (full overwrite)
  • PATCH /admin/clients/:client_id — Partial update (optional)
  • DELETE /admin/clients/:client_id — Delete or deactivate clients
  • GET /admin/audits - Get all audit events
  • GET /admin/audits/clients/:client_id - Get all audit events for a specific client
  • GET /admin/audits?type={event_type} - Get all audit events by type.

Contributor guide

Research direction
Review the related files (middleware.go, routes.go, roles.go) to understand the existing routing and middleware patterns. Implement the listed endpoints, ensuring proper authentication and authorization checks. Add documentation for each endpoint.
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.
2
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.
Active
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.
65