onaio/onadata

Add an audit trail to capture which user updates the require authentication option for an organization

Open

#2,553 opened on Feb 15, 2024

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Python (143 forks)auto 404
DiscussionGood First Issue

Repository metrics

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

Description

Suggested Feature / Enhancement

Currently, a user with a appropriate permissions to change the settings for an organization can update the require authentication option. The option impacts whether users need to sign in with their Ona accounts before accessing and submitting data to forms using ODK Collect and Enketo web forms.

If the option is switched off, there is no way of finding out which user did it. We need to trail the changes made to this setting.

Benefits of implementing the feature/enhancement

Keep track of which users enable/switch off authentication for an organization

Suggested implementation plan(Steps to be taken to implement feature)

Contributor guide

Research direction
Identify the view or serializer that handles updating the 'require authentication' setting for an organization, and add a log entry (e.g., using Django's logging or a separate audit model) recording which user made the change and the previous/current value.
Tech stack
python
Domain
backendapi
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonDjango
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60