LL-332

[erikajledesma]

In this PR/ticket, Google login OAuth flow has been added along with existing GitHub login functionality. The Dockerfile in the routes directory has also been modified to start both Google and GitHub Express servers. This allows the user to be able to log in with either Google or GitHub and see their profile information displayed to them once they log in and pass the consent screen.

Subsequent # (issue): LL-332

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Before testing, ask @erikajledesma to add your gmail as a test user to Google Console API.

1. Place .env file in /routes directory (ask @erikajledesma or @aematei for the file)
2. Run cd src/routes to get to routes directory
3. Run docker compose build
4. Run docker compose up
5. Go to PORTS > link hosted at port 3000 if using codespaces (localhost will be an IP address if running on VSCode)
6. Log in with Google
7. Accept the consent screen
8. When redirected, replace https://localhost:5000 with the name of your codespace or IP address. Make sure to copy the forwarded link hosted on port 5000.
9. Check to see if JSON file is returned with your profile information.

Checklist (when relevant):

• My code follows the style guidelines of this project

  TypeScript
  Python
  Schema

• I have included a reviewer on the pull request [Replace this text with the reviewer]

• I have performed a self-review of my own code

• I have commented my code, particularly in hard-to-understand areas

• I have made corresponding changes to the documentation

• My changes generate no new warnings

• I have added tests that prove my fix is effective or that my feature works

• New and existing unit tests pass locally with my changes

• Any dependent changes have been merged and published in downstream modules

[pogi7]

lgtm!

[vliu36]

Works for me! But one of the gh action checks have failed @erikajledesma.

[vliu36]

Works for me! Just need to fix merge conflicts and rerun the python workflows.