vigiloauth/vigilo

Add public endpoint to fetch system security questions

Open

#372 opened on Jun 3, 2025

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Go (9 forks)auto 404
good first issuepriority: mediumtask

Repository metrics

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

Description

Description: Brief description of what needs to be implemented and why.

User Story: As a user I want to see a list of available security questions So that I can select one during registration or account recovery

Endpoint/Component: This section can be deleted if not applicable to this feature.

  • Method: GET
  • Path: /security-questions

Example Response:

[
  {
    "id": 1,
    "question": "What was the name of your first pet?"
  },
  {
    "id": 2,
    "question": "What is your mother’s maiden name?"
  },
]

Acceptance Criteria:

  • Endpoint is publicly accessible (does not require authentication)
  • Returns only question IDs and their text (no answers or sensitive data)
  • Questions are fetched from system-configured seed data

Testing Requirements:

  • Unit Tests: Ensure the service returns expected data structure
  • Integration Tests: Validate the route returns correct data with proper status codes

Contributor guide

Research direction
Create a new GET endpoint at /security questions that returns a hardcoded or database seeded list of security questions. Ensure it's public (no auth) and includes unit/integration tests.
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.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
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
GoHTTPJSON
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90