Feat/samvritsrinath firebase auth #18
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…g the intended function
… not being called
…go _id in route, currently only sending uid firebase auth fully functional, need to send mongo id in addition to firerbase UID from backend
merging with main
benjaminJohnson2204
requested changes
Feb 15, 2024
benjaminJohnson2204
requested changes
Feb 15, 2024
benjaminJohnson2204
approved these changes
Feb 15, 2024
Syu125
approved these changes
Feb 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tracking Info
Resolves #8
Changes
usermongo model withroleanduidfields/login/api/whoamithat uses the sender's JWT token to verify identity, and returns the user's role and uid if that user exists in the database; this route is called upon hitting the login button on the frontendTesting
We added console statements that printed out the user information received from the backend, which we took a screenshot of in the Javascript console. Furthermore, a dummy page was set up that the login page routed to after the call to the backend was resolved. The page was also checked on a mobile device
Confirmation of Change