Skip to content

BE41: Secure HTTPS Environment & User Ownership Enforcement#263

Open
TienNguyen3711 wants to merge 1 commit intomasterfrom
pr/api-user-boundaries
Open

BE41: Secure HTTPS Environment & User Ownership Enforcement#263
TienNguyen3711 wants to merge 1 commit intomasterfrom
pr/api-user-boundaries

Conversation

@TienNguyen3711
Copy link
Copy Markdown
Collaborator

Summary

  • require authentication on user-scoped appointment, shopping list, recipe, chatbot, account, and water intake routes
  • resolve target user IDs from req.user.userId for normal users, with override support only for privileged roles
  • enforce ownership checks for appointment updates/deletes and shopping list item mutations

What files changed

  • routes/account.js
  • routes/appointment.js
  • routes/chatbot.js
  • routes/recipe.js
  • routes/shoppingList.js
  • routes/waterIntake.js
  • controller/accountController.js
  • controller/appointmentController.js
  • controller/chatbotController.js
  • controller/recipeController.js
  • controller/shoppingListController.js
  • model/appointmentModel.js
  • services/shoppingListService.js
  • validators/appointmentValidators.js
  • validators/recipeValidator.js
  • validators/shoppingListValidator.js

Testing

  • node -c controller/appointmentController.js
  • node -c services/shoppingListService.js
  • node -c controller/chatbotController.js
  • node -c controller/recipeController.js
  • node -c routes/waterIntake.js
  • node -c controller/accountController.js
  • not run end-to-end

@TienNguyen3711 TienNguyen3711 changed the title Harden authenticated user data boundaries BE41: Secure HTTPS Environment & User Ownership Enforcement May 10, 2026
@TienNguyen3711 TienNguyen3711 requested a review from datnq2001 May 10, 2026 14:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant