This PMS that is Property management system is the simple UI to discover the perfect Propert for your needs with our user-friendly tool that compares multiple Propert offerings. It is designed to allow users to compare between multiple properties from different places and find the right propert to get your household or businesses place.
Objective:
The objective of this issue is to create middleware guards using the express framework that enforce role-based authentication for specific routes and functionalities in the Property Management System, which is built using JavaScript, Express, and TypeScript.
Tasks:
Develop middleware guards that check the user's role based on the JWT token.
Apply these middleware guards to routes that require role-based authentication.
Ensure that unauthorized users are denied access to restricted routes.
Update relevant documentation with the changes made.
Acceptance Criteria:
Middleware guards should correctly check and enforce role-based authentication.
Unauthorized users should be denied access to routes requiring specific roles.
The relevant parts of the documentation should reflect the changes made.
Objective:
The objective of this issue is to enhance security by implementing password hashing using bcrypt when creating a new user in the Property Management System.
Tasks:
Add the bcrypt library as a project dependency.
Modify the user creation process to hash the user's password using bcrypt.
Ensure that the hashed password is securely stored in the database.
Update relevant documentation with the changes made.
Acceptance Criteria:
New users should have their passwords securely hashed using bcrypt during registration.
The application should successfully create users with hashed passwords.
The relevant parts of the documentation should reflect the changes made.
Objective:
The objective of this issue is to create an authentication endpoint using JSON Web Tokens (JWT) to facilitate role-based authentication for users in the Property Management System.
Tasks:
Create an authentication endpoint that accepts user credentials (e.g., username and password).
Verify user credentials and generate a JWT token if authentication is successful.
Include user role information in the JWT payload.
Implement role-based access control based on the user's role.
Update relevant documentation with the changes made.
Acceptance Criteria:
Users should be able to authenticate and receive a JWT token upon successful login.
JWT tokens should contain user role information.
Access to certain functionalities should be restricted based on user roles.
The relevant parts of the documentation should reflect the changes made.
Objective:
The objective of this issue is to implement authentication guards in various endpoints, including create, update, and delete operations, to enforce role-based authentication in the Property Management System, which is built using JavaScript, Express, and TypeScript.
Tasks:
Identify the relevant endpoints for create, update, and delete operations.
Apply the role-based authentication guard to these endpoints.
Ensure that only authorized users with the appropriate roles can perform these actions.
Update relevant documentation with the changes made.
Acceptance Criteria:
Authentication guards should be successfully applied to create, update, and delete endpoints.
Unauthorized users should be prevented from performing these actions.
The relevant parts of the documentation should reflect the changes made.