streamaserver/streama

Remove profiles from anonymous access?

Open

#759 opened on Apr 6, 2019

View on GitHub
 (6 comments) (0 reactions) (0 assignees)JavaScript (977 forks)batch import
DiscussionHelp wanted

Repository metrics

Stars
 (9,565 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

aswell with view state from database anonymous users should not modify anything on database at al, just access

Contributor guide

Research direction
Examine the codebase to understand how anonymous users are currently handled. Look for authentication middleware (likely in a Node.js/Express setup) that controls access to routes related to profiles and view state. Check the database schema for tables storing profiles and view state. The issue mentions removing these from anonymous access, so likely need to modify route guards or add authorization checks to reject anonymous users from modifying those resources. No linked PRs or maintainer responses provide additional guidance, so start by tracing the routes for profile management and view state updates.
Tech stack
javascript
Domain
securityauthenticationbackend
Issue type
Security
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Unclear
Prerequisites
understanding of the application's authentication flowknowledge of database queries for user profiles and view state
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30