Describe the bug
Currently, if you have an account signed in using Google OAuth and you try to sign in using that same email, but through a different OAuth provider (Github), you are not allowed to sign in despite it being the same email. For ease of use, we want to enable account linking (so long as they are the same email under different Auth providers) for development experience only.
Steps to reproduce:
Must build locally (do not use the Gitpod setup)
Please use this guide to set up the dev environment locally.
Sign in and make an account using the Google provider option
Sign out
Sign in to the Classroom App again using a different provider option, but make sure it still falls under the auth0 options (for example, Github). The Github account must be associated with the same Gmail address as when you signed in on step 3. (For example, your Gmail used in step 3 is coolcoder123@gmail.com, and your GitHub account also needs to have the email address:coolcoder123@gmail.com
Current Behavior:
Step 5 fails with an unclear error message: "Cannot verify identity" (I don't remember the exact error message).
Desired Behavior:
Allow account linking between different providers but only for development experience. If the need arises (through user feedback), we can attempt to implement a much safer option for end-users to also have this experience.
Describe the bug Currently, if you have an account signed in using Google OAuth and you try to sign in using that same email, but through a different OAuth provider (Github), you are not allowed to sign in despite it being the same email. For ease of use, we want to enable account linking (so long as they are the same email under different Auth providers) for development experience only.
Steps to reproduce:
coolcoder123@gmail.com
, and your GitHub account also needs to have the email address:coolcoder123@gmail.com
Current Behavior:
Desired Behavior:
This document also explains how to reproduce