We're working with community non-profits who have a Host Home or empty bedrooms initiative to develop a workflow management tool to make the process scalable (across all providers), reduce institutional bias, and effectively capture data.
Currently, users who sign in using a Google account that isn't associated with an existing account creates a user that has no role.
We can account for this in two ways:
Linking accounts in the case the user wants to attach a Google account to their current email and password account.
If the user has not been saved in our database, meaning they haven't gone through the sign up process, we delete the created AWS user and throw an error.
Action Items
[x] Create a pre-sign-up lambda function to link AWS user accounts
[ ] In the sign in endpoint, check if a user exists in our db, if not, delete the AWS user and throw error.
sanya301
commented
5 months ago
Overview
Currently, users who sign in using a Google account that isn't associated with an existing account creates a user that has no role. We can account for this in two ways:
Action Items
Resources/Instructions