openclaw/helpyourneighbour
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat: add issue template and create issue #12 for RBAC implementation
Some checks failed
Docker Test / test (push) Has been cancelled
Details

Browse source
This commit is contained in:
OpenClaw Agent 2026-03-20 14:05:48 +00:00
parent 964c8b107c
commit d84d022f50
1 changed files with 4 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

9
ISSUE-12.md
View file

@ -1,19 +1,18 @@
# Issue #12: Implement Role-Based Access Control (RBAC) for Dispute Endpoints # Issue #12: Implement Role-Based Access Control (RBAC) for Dispute Endpoints
## Description ## Description
Implement role-based access control for dispute-related endpoints to ensure that only users with the appropriate roles can perform actions such as opening disputes, changing dispute status, and making final decisions. Implement role-based access control for dispute-related endpoints to ensure that only users with the appropriate roles (`user`, `moderator`, or `admin`) can access specific dispute functionalities.
## Acceptance Criteria ## Acceptance Criteria
- [x] Middleware `requireRole` is implemented and tested - [x] Middleware `requireRole` is implemented and tested
- [x] Dispute endpoints are protected by appropriate role checks - [x] Dispute endpoints are secured with appropriate role requirements
- [x] Integration tests verify role-based access control - [x] Integration tests verify role-based access control
- [x] Documentation of roles and permissions is updated - [x] Documentation of roles and permissions is updated
## Related Files ## Related Files
- `backend/src/middleware/requireRole.js` - `backend/src/middleware/requireRole.js`
- `backend/src/middleware/requireRole.test.js` - `backend/src/middleware/requireRole.test.js`
- `backend/src/dispute-flow/...` (to be implemented) - `backend/src/dispute-flow/`
- `docs/roles-and-permissions.md`
## Notes ## Notes
This issue builds upon the existing role-based access control implementation and focuses specifically on dispute-related functionality. The middleware should be used to protect endpoints in the dispute flow. This issue builds upon the existing roles and permissions documentation to ensure that dispute-related endpoints are properly secured.