jambonz / jambonz/jambonz-api-server
Introduce read-only users in jambonz webapp
Open
- Dominant language
- JavaScript
- Stars
- 24
- Forks
- 38
- Avg merge
- 8h 34m
- Merged PRs (30d)
- 1
Description
Currently all users created can perform CRUD operations based on the scope, it will be useful to introduce read-only users who can view the configurations but cannot create/modify/delete.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how user scopes are represented and enforced across the jambonz REST APIs, focusing on the existing CRUD authorization paths. Define how a read-only user is created and how each configuration operation should behave; done means such users can view configurations but cannot create, modify, or delete them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, authorization, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100