Currently, the kitchen dashboard page can be accessed by anyone, bypassing authentication or route protection. This poses a security risk, as sensitive kitchen operations should only be accessible to authorized users.
Expected Behavior:
The kitchen dashboard should only be accessible to authenticated users.
Implement a passkey or similar mechanism to further secure the route if necessary.
Steps to Reproduce:
Navigate to the /kitchen-dashboard route.
Observe that it is accessible without any authentication.
Proposed Solution:
Implement authentication middleware or route guard for /kitchen
Add an additional layer of security (e.g., passkey) if required for enhanced protection.
Additional Context:
The security of the kitchen dashboard is crucial for ensuring that only authorized personnel can view or modify sensitive kitchen operations.
Currently, the kitchen dashboard page can be accessed by anyone, bypassing authentication or route protection. This poses a security risk, as sensitive kitchen operations should only be accessible to authorized users.
Expected Behavior:
The kitchen dashboard should only be accessible to authenticated users.
Implement a passkey or similar mechanism to further secure the route if necessary.
Steps to Reproduce:
Navigate to the /kitchen-dashboard route.
Observe that it is accessible without any authentication.
Proposed Solution:
Implement authentication middleware or route guard for /kitchen
Add an additional layer of security (e.g., passkey) if required for enhanced protection.
Additional Context:
The security of the kitchen dashboard is crucial for ensuring that only authorized personnel can view or modify sensitive kitchen operations.