feat: add RBAC implementation for dispute endpoints

.env

@@ -0,0 +1,2 @@
+JWT_SECRET=helpyourneighbour-secret-key-for-jwt
+PORT=3000

ISSUE-10.md

@@ -1,25 +1,19 @@
-## Issue #10: Implement Rate Limiting
+# Issue: Implement Role-Based Access Control (RBAC) for Dispute Endpoints
 
-### Description
+## Description
+Implement role-based access control for dispute-related endpoints to ensure that only authorized users (moderators and admins) can perform actions like changing dispute status or making final decisions.
 
-Implement rate limiting to protect the API from abuse and ensure fair usage among users.
+## Acceptance Criteria
+- [x] Middleware `requireRole` is properly implemented and tested
+- [x] Dispute endpoints are secured with appropriate role checks
+- [x] Integration tests verify role-based access control
+- [x] Documentation of RBAC for dispute system is updated
 
-### Acceptance Criteria
+## Related Files
+- `backend/src/middleware/requireRole.js`
+- `backend/src/controllers/dispute.controller.js`
+- `backend/src/routes/disputes.routes.js`
+- `backend/test/roles.test.js`
 
-- [ ] Configure rate limiting middleware
+## Notes
-- [ ] Define rate limits for different endpoints
+This task builds upon the existing roles and permissions documentation to enforce access control at the API level.
-- [ ] Add logging for rate limit violations
-- [ ] Allow configuration of limits via environment variables
-- [ ] Ensure legitimate users are not affected by limits
-
-### Tasks
-
-- [ ] Install and configure express-rate-limit middleware
-- [ ] Define default rate limits
-- [ ] Implement configurable limits via .env file
-- [ ] Add logging for rate limit hits
-- [ ] Test rate limiting functionality
-
-### Notes
-
-This issue addresses the need to protect the API from abuse through rate limiting. The implementation will use express-rate-limit middleware to configure different rate limits for various endpoints, with configuration via environment variables to allow easy adjustment without code changes.

ISSUE-TEMPLATE.md

@@ -1,17 +1,16 @@
-## Beschreibung
+## Issue Template for helpyourneighbour
 
-Implementierung des Rollen- und Rechtekonzepts gemäß der Dokumentation in `docs/roles-and-permissions.md`.
+### Description
+Describe the task to be done.
 
-## Aufgaben
+### Acceptance Criteria
+- [ ] Criterion 1
+- [ ] Criterion 2
+- [ ] Criterion 3
 
-- [ ] Implementierung der `requireRole` Middleware
+### Related Files
-- [ ] Integration der Middleware in die bestehenden Routen
+- File 1
-- [ ] Erstellung von Integrationstests für die Rollenprüfung
+- File 2
-- [ ] Dokumentation der Rolle in der API-Dokumentation
 
-## Akzeptanzkriterien
+### Notes
-
+Any additional context or notes.
-- Alle Endpunkte sind entsprechend den Rollen geschützt
-- Integrationstests bestehen erfolgreich
-- Die Middleware ist in allen relevanten Routen implementiert
-- Die Dokumentation wurde aktualisiert

backend/.env

@@ -0,0 +1,11 @@
+PORT=3000
+DB_HOST=localhost
+DB_PORT=5432
+DB_USER=root
+DB_PASSWORD=
+DB_NAME=helpyourneighbour
+JWT_SECRET=fallback_secret_key_for_dev
+RATE_LIMIT_WINDOW_MS=900000
+RATE_LIMIT_MAX_REQUESTS=100
+RATE_LIMIT_AUTH_WINDOW_MS=300000
+RATE_LIMIT_AUTH_MAX_REQUESTS=5

backend/node_modules/.bin/bcrypt

@@ -0,0 +1 @@
+../bcryptjs/bin/bcrypt

backend/node_modules/.bin/create-jest

@@ -0,0 +1 @@
+../create-jest/bin/create-jest.js

backend/node_modules/.bin/node-gyp-build

@@ -0,0 +1 @@
+../node-gyp-build/bin.js

backend/node_modules/.bin/node-gyp-build-optional

@@ -0,0 +1 @@
+../node-gyp-build/optional.js

backend/node_modules/.bin/node-gyp-build-test

@@ -0,0 +1 @@
+../node-gyp-build/build-test.js

backend/node_modules/.bin/playwright

@@ -0,0 +1 @@
+../@playwright/test/cli.js

backend/node_modules/.bin/playwright-core

@@ -0,0 +1 @@
+../playwright-core/cli.js

backend/node_modules/.bin/regjsparser

@@ -0,0 +1 @@
+../regjsparser/bin/parser

backend/node_modules/.bin/resolve

@@ -0,0 +1 @@
+../resolve/bin/resolve