User Story
As a user, I would like to securely access my profile and history information, so that I can safely view my personal details.
Description
This issue involves making adjustments to the frontend /profile and /history routes (and all related) of the app to include authentication and authorization capabilities, intended to ensure that profiles/history can only be viewed/edited/deleted by the user who owns them. The information shown should be taken from the authenticated user (as opposed to the current method of using a profile atom).
This is a follow-up issue to #69 from Sprint 2.
Acceptance Criteria
[x] authentication middleware to ensure only the specific user can access their profile and history information
[x] logged in users should see the info belonging to them
Testing
[x] ensure information retrieved is what is expected
[x] test updating and subsequent retrieving to ensure save occurred
User Story As a user, I would like to securely access my profile and history information, so that I can safely view my personal details.
Description This issue involves making adjustments to the frontend
/profileand/historyroutes (and all related) of the app to include authentication and authorization capabilities, intended to ensure that profiles/history can only be viewed/edited/deleted by the user who owns them. The information shown should be taken from the authenticated user (as opposed to the current method of using a profile atom).This is a follow-up issue to #69 from Sprint 2.
Acceptance Criteria
Testing