Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

User Authentication #3

Open
4 tasks
jaydenpersonnat opened this issue Sep 27, 2023 · 0 comments
Open
4 tasks

User Authentication #3

jaydenpersonnat opened this issue Sep 27, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@jaydenpersonnat
Copy link
Collaborator

jaydenpersonnat commented Sep 27, 2023

Resources

Description

We want to move from the starter project's "magic link" login system to a traditional email/password structure, with email verification through Supabase.

For now, feel free to style forms and/or pages as much or as little as you like, though note we may need to modify styling when designers submit lo-fis.

  • Modify the existing login flow in app/#
    • Request both an email and password.
    • Take advantage of Supabase's authentication methods! (see Supabase docs)
    • Add appropriate error checking and communication for missing fields and incorrect emails/passwords.
    • Supabase seems to hash passwords with bcrypt already, so don't worry about doing it yourself here (or in #) for now.
  • Create a # flow in a new folder app/#
    • Create a page.tsx file that contains content displayed. Feel free to create additional files as needed.
    • Users should submit an email, password (with confirmation), as well as whether they are registering as a patient or a
      clinician. You can do this via a checkbox or something similar, and inserting a row into the patient or clinician table as
      appropriate.
    • Collect other relevant information. First and last name should be required, but anything else should be optional, and
      dependent on the type of user registering:
      • Patients
        • First name
        • Last name
        • Age
        • State
        • City
        • Zip code
      • Clinicians
        • First name
        • Last name
        • Employer
        • State
        • City
        • Zip code
    • You can take advantage of Supabase's verification and options to # with user metadata (see Supabase docs).
    • Users should still need to verify their email when first signing up (see Supabase docs).
    • Add appropriate error checking and communication for missing or invalid fields.
  • Ensure sessions and public/private routes still function as expected.

Stretch Goal - Log in with Google

(Only if you've finished everything above and are still itching for more! If you don't get to this, that's okay too.)

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants