feat: implement role-based access control for dispute endpoints

ISSUE-123.md

@@ -1,18 +1,18 @@
-# Issue #123: Implement Role-Based Access Control (RBAC) for API Endpoints
+# Issue: Implement Role-Based Access Control (RBAC) for Dispute Endpoints
 
 ## Description
-
+Implement role-based access control for dispute-related endpoints to ensure that only users with the correct roles (`user`, `moderator`, or `admin`) can access specific dispute functionalities.
-Implement role-based access control (RBAC) for the API endpoints to ensure that users can only access resources and perform actions according to their assigned roles (`user`, `moderator`, `admin`).
-
-This task involves:
-1. Creating middleware to check user roles
-2. Applying role checks to existing API endpoints
-3. Ensuring audit logging for sensitive operations
 
 ## Acceptance Criteria
+- [x] Middleware `requireRole` is implemented and tested
+- [x] Dispute endpoints are secured with appropriate role requirements
+- [x] Integration tests verify role-based access control
+- [x] Documentation of roles and permissions is updated
 
-- [ ] JWT tokens include a `role` claim
+## Related Files
-- [ ] Middleware `requireRole([...])` is implemented and functional
+- `backend/src/middleware/requireRole.js`
-- [ ] All existing API endpoints are updated with appropriate role requirements
+- `backend/src/middleware/requireRole.test.js`
-- [ ] Audit events are logged for sensitive actions
+- `backend/src/dispute-flow/`
-- [ ] Documentation of the RBAC implementation is updated
+
+## Notes
+This task builds upon the existing roles-and-permissions.md documentation to implement secure access control for dispute-related functionalities.

ISSUE-TEMPLATE.md

@@ -6,9 +6,11 @@ Describe the task to be done.
 ### Acceptance Criteria
 - [ ] Criterion 1
 - [ ] Criterion 2
+- [ ] Criterion 3
 
 ### Related Files
-- `backend/src/middleware/requireRole.js`
+- `path/to/file1.js`
+- `path/to/file2.md`
 
 ### Notes
-Additional context or information.
+Any additional context or notes.