Adds Google as an Authentication method #669

shayneczyzewski · 2022-07-14T21:50:41Z

Description

This change adds Google as a new AuthN method. It does so by creating a new Entity, externalAuthAssociationEntity that associates an external user with an internal user.

Demo

Here is an example if you want to play around with it: https://wasp-csrf-demo.netlify.app/ (Note: I'm using the old Cookies project but it is using this branch and JWTs). I added everyone's email to the Google project, which you have to do if unpublished, but let me know if you get some error about access when signing in with Google.

Syntax

The syntax for auth is updated, to look like this when fully specified:

  auth: {
    userEntity: User,
    externalAuthEntity: SocialLogin,
    methods: {
      usernameAndPassword: {},
      google: {
        configFn: import { config } from "@ext/auth/google.js",
        getUserFieldsFn: import { getUserFields } from "@ext/auth/google.js"
      }
    },
    onAuthFailedRedirectTo: "/login",
    onAuthSucceededRedirectTo: "/profile"
  },

...

entity User {=psl
    id                        Int           @id @default(autoincrement())
    username                  String        @unique
    password                  String
    externalAuthAssociations  SocialLogin[]
psl=}

entity SocialLogin {=psl
  id          Int       @id @default(autoincrement())
  provider    String
  providerId  String
  user        User      @relation(fields: [userId], references: [id], onDelete: Cascade)
  userId      Int
  createdAt   DateTime  @default(now())
  @@unique([provider, providerId, userId])
psl=}

OAuth Flow

The OAuth flow used here is as follows:

User navigates to: https://wasp-csrf-demo.netlify.app/login
When clicking the Google login button, a GET request to the API server happens: https://wasp-csrf-demo.herokuapp.com/auth/external/google/login
The API server then constructs a redirect URL, and redirects the browser to: https://accounts.google.com/o/oauth2/v2/auth/oauthchooseaccount?response_type=code&redirect_uri=https%3A%2F%2Fwasp-csrf-demo.netlify.app%2Fauth%2Flogin%2Fgoogle&scope=email%20profile&client_id=213102658416-49aoc8onkqj44e8o3cbnqtbmvel4plml.apps.googleusercontent.com&flowName=GeneralOAuthFlow
After login, Google will redirect to the frontend with a code, like so: https://wasp-csrf-demo.netlify.app/auth/login/google?code=4%2F0AdQt8qjMwXABj01-i3MOwy9o8OkxWg4z6dxwcxaNPf6WfgEsmb1v4XNmU_EskVypkI7jHQ&scope=email+profile+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile+openid+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email&authuser=0&prompt=none
5a) The React page on the frontend takes this URL, and issues an AJAX GET request to the API server with the same query string: https://wasp-csrf-demo.herokuapp.com/auth/external/google/validateCode?code=4%2F0AdQt8qjMwXABj01-i3MOwy9o8OkxWg4z6dxwcxaNPf6WfgEsmb1v4XNmU_EskVypkI7jHQ&scope=email+profile+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile+openid+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email&authuser=0&prompt=none
5b) The API server takes the code, and Passport talks directly to Google in a server-to-server communication. After that succeeds, it returns the JWT for the authenticated user back to the frontend.

Notes

A couple of things to note:

There was a bug in a downstream dependency (node-oauth) of our Passport Google library, but it wasn't being updated. Therefore, I had to introduce: https://www.npmjs.com/package/patch-package
There are default functions for both configuration and user fields, if the user does not supply them: https://github.com/wasp-lang/wasp/blob/shayne-jwt-authn-google/waspc/data/Generator/templates/server/src/routes/auth/passport/google/googleDefaults.js
- So in a minimal configuration, they just need to add google: {} to the auth.methods, a externalAuthEntity, one line to userEntity and add 2 environment variables 🪄
This auth method should not require usernameAndPassword.
This auth method gives user a button and a URL they can easily use to build their login page.
I added a notion of googleConfig.js so google.js and googleDefaults.js could be pure JS.
I tried to use a generic term, External Auth, vs Passport, when doing generic things to not tie it to the implementation. When operating on Passport things directly, I just said Passport.

Closes #667
Closes #575

Type of change

⚠️ WARNING: This is a breaking change, since we updated auth.methods syntax, now add a new required env var when deploying (WASP_WEB_CLIENT_URL for CORS protection, as well as knowing where to redirect from on the server), and updated the Docker base image. ⚠️

Please select the option(s) that is more relevant.

Code cleanup
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

waspc/data/Generator/templates/react-app/src/auth/buttons/Google.js

waspc/data/Generator/templates/react-app/src/auth/useAuth.js

waspc/examples/todoApp/todoApp.wasp

waspc/src/Wasp/Generator/Common.hs

Martinsos

Awesome, excited about this :)!

One note, that I dealt with on a previous project so I immediately remembered it: it is dangerous to allow both email/password and any other auth method for a user if email verification is not used, since it can be used to hijack an account. So for example, if [email protected] logged in with google account, and then somebody else decided to sign up with the [email protected] via email and password and as a result got connected to that same user account, but we didn't verify they own the email, we just gave them access to the user account that is not theirs. You don't have that issue though, first of all because they can't do it at all right now since there is no password resetting :D, but once we have it, we are also ok because password resetting forces them to prove it is their email. So we are ok in that scenario.
What about the other direction hm -> let's say an attacker A created an account with email that is not theirs, and then somebody B who owns that email logs in via Google later. Now the problem is that both A and B have access to the account, while B might not be aware of it! We might be affected by this right now I think?

The solution is to introduce email verification, then we are safe.
What until then? Maybe we can just reset password in any case -> so if account already exists, we also reset password. This disables password login until they reset the password. Since we don't even have reset currently, it means it disables auth via password completely, but I think that is ok in this situation where we are still missing features.

Generally, this is looking awesome :)!!! Reviewed it all, looks great, I did leave a bunch of comments but nothing major, so we can go through those but generally all good from my side!

I just realized now we don't have password reset or email verification steps -> what about that, when should we implement that? Hmmmm. Tricky thing is that smth to send emails is needed, some kind of emailer. I am not sure if any server can just send them? Ok, this is beyond scope of this PR.

waspc/data/Generator/templates/Dockerfile

waspc/data/Generator/templates/react-app/src/auth/buttons/Google.js

waspc/data/Generator/templates/react-app/src/auth/pages/OAuthCodeExchange.js

web/docs/integrations/google.md

web/docs/language/features.md

shayneczyzewski

Thanks so much for all the great questions, comments, and suggestions @Martinsos! I appreciate it. I replied to them all, and will start working on them shortly.

Per your two other notes:

Good point on still allowing the first user who signed up for the email to log in. I think we could either:

change the password on every Google login, as suggested, or
we could add a field to the User entity that tracks what login method can be used. it would start as usernameAndPassword but the minute they used any other auth method, it would change and they could only use that moving forward. however, that does introduce a bit of complexity and requires us to either change the model for them or ask them to update it themselves. additionally, most of this goes away once we do email validation and password reset in the future.

So for now, I think the best way is just to update the password on login by Google.

I just realized now we don't have password reset or email verification steps -> what about that, when should we implement that? Hmmmm. Tricky thing is that smth to send emails is needed, some kind of emailer. I am not sure if any server can just send them? Ok, this is beyond scope of this PR.

Since this is already getting pretty big and complex, I agree we should punt on that. I think this will give users some real value/buzz, and we can later add those incrementally over time.

Thanks again!

waspc/data/Generator/templates/react-app/src/auth/buttons/Google.js

waspc/data/Generator/templates/react-app/src/auth/pages/OAuthCodeExchange.js

web/docs/integrations/google.md

web/docs/language/features.md

Martinsos · 2022-07-20T13:18:44Z

Thanks so much for all the great questions, comments, and suggestions @Martinsos! I appreciate it. I replied to them all, and will start working on them shortly.

Per your two other notes:

Good point on still allowing the first user who signed up for the email to log in. I think we could either:

change the password on every Google login, as suggested, or

we could add a field to the User entity that tracks what login method can be used. it would start as usernameAndPassword but the minute they used any other auth method, it would change and they could only use that moving forward. however, that does introduce a bit of complexity and requires us to either change the model for them or ask them to update it themselves. additionally, most of this goes away once we do email validation and password reset in the future.

So for now, I think the best way is just to update the password on login by Google.

I just realized now we don't have password reset or email verification steps -> what about that, when should we implement that? Hmmmm. Tricky thing is that smth to send emails is needed, some kind of emailer. I am not sure if any server can just send them? Ok, this is beyond scope of this PR.

Since this is already getting pretty big and complex, I agree we should punt on that. I think this will give users some real value/buzz, and we can later add those incrementally over time.

Thanks again!

soudns good let's just reset the password on google login!

Martinsos

Responded to everything!

shayneczyzewski

Thanks for the feedback @Martinsos! I believe I addressed it all, but will do another quick scan through tomorrow just to make sure. I will also start doing some permutation testing to make sure I didn't break anything and it works without emailAndPassword, etc. Appreciate it!

waspc/data/Generator/templates/server/src/routes/auth/passport/google/google.js

waspc/src/Wasp/AppSpec/App/Auth.hs

waspc/src/Wasp/Generator/ServerGenerator.hs

web/docs/language/features.md

waspc/data/Generator/templates/server/src/core/auth/prismaMiddleware.js

waspc/data/Generator/templates/react-app/src/auth/buttons/Google.js

waspc/data/Generator/templates/react-app/src/auth/pages/OAuthCodeExchange.js

waspc/data/Generator/templates/react-app/src/router.js

waspc/data/Generator/templates/server/src/routes/auth/passport/google/google.js

Martinsos

LGTM!! I left a couple of small comments, but otherwise all good from my side! Auth is coming :D!!!

waspc/data/Generator/templates/react-app/src/auth/pages/OAuthCodeExchange.js

waspc/data/Generator/templates/server/src/core/auth.js

waspc/data/Generator/templates/server/src/routes/auth/passport/google/google.js

Martinsos · 2022-07-21T18:30:14Z

waspc/data/Generator/templates/server/src/routes/auth/passport/google/googleDefaults.js

@@ -0,0 +1,26 @@
+import { upsertUserWithRandomPassword } from '../../../../core/auth.js'
+
+// Default implementation if there is no `auth.methods.google.configFn`.


Ha reference to Wasp-lang! We avoided that in the rest of the code so far. But we said we will be less careful about that. So ok, if you think it is useful, let's leave it!

haha Yeah, I was kinda hesitant to do so, but this file is pretty unique in that I actually link to it from the documentation to show users what the default implementation is, so I think in that context it may be ok. 😅

Hm, maybe I should have put it here then? That's also a default implementation used only if the users don't define their own.

Perhaps, but maybe only if you link to it from the docs? The comment itself may not be a great idiom, I'm not sold on it entirely, but figured it would help users who want to see the default but are unsure where they can override in the wasp file.

I would keep lower, it doesn't hurt and it communicates intent / documents a bit.

waspc/src/Wasp/Generator/ServerGenerator.hs

shayneczyzewski · 2022-08-31T17:14:44Z

waspc/data/Generator/templates/server/src/routes/auth/passport/google/google.js

+// This token was used to get the Google profile information supplied as a parameter.
+// We add the Google profile to the request for downstream use.
+async function addGoogleProfileToRequest(req, _accessToken, _refreshToken, googleProfile, done) {
+  req.wasp = { ...req.wasp, googleProfile }


I tried to really simplify this function to just give us back the google profile (by adding it to the request). This makes it easier to follow the downstream usage and flow I think.

Why does it take these extra ignored params?

It is just the shape of the callback for Google's Passport implementation. The library invokes this.

waspc/data/Generator/templates/server/src/routes/auth/passport/google/google.js

waspc/data/Generator/templates/server/src/routes/auth/passport/google/googleDefaults.js

waspc/data/Generator/templates/server/src/routes/auth/utils.js

waspc/examples/todoApp/todoApp.wasp

waspc/src/Wasp/AppSpec/Valid.hs

shayneczyzewski · 2022-09-01T13:54:04Z

waspc/examples/todoApp/todoApp.wasp

@@ -8,7 +8,14 @@ app todoApp {
  ],
  auth: {
    userEntity: User,
-    methods: [ UsernameAndPassword ],
+    // externalAuthAssociationEntity: SocialLogin,


NOTE: I am disabling Google auth by default in the todo app, just so server won't crash if you don't have the Google project envars.

shayneczyzewski · 2022-09-01T15:21:20Z

Ok @Martinsos and @sodic, I think this is ready for a final review. The main update here is we no longer intertwine Google authn with any email field (it's now username, anyway :D) and instead we use an externalAuthAssociationEntity to link any 3rd party auth with an internal user. It will generate a random username as part of the first login process, and I made one of those cutesy Heroku-like functions to do it (say hello to "first-green-crab-88221" lol).

Please let me know if you have any questions about this update, and thanks for sticking with me through basically three reviews :) (cookies, JWT with EmailAndPassword, and now JWT with usernameAndPassword). In the end, I think we have the right approach. 🙏🏻

sodic

Great work once again!

I left a lot of comments, but none that would require mandatory changes. Take a look, see which make sense and merge when ready!

waspc/src/Wasp/Analyzer/TypeDefinitions/TH/Decl.hs

waspc/data/Generator/templates/server/src/core/auth.js

waspc/data/Generator/templates/server/src/routes/auth/passport/google/google.js

sodic · 2022-09-02T15:12:14Z

web/docs/language/features.md

+  export async function getUserFields(_context, args) {
+    const username = await generateAvailableUsername(args.profile.displayName.split(' '), { separator: '.' })
+    return { username }
+  }


Good idea allowing them to define their own username-derivation function!

One question, if we support Google and know how its args look like, maybe we could provide this as a default implementation instead of Heroku animals.

That is a good question! I know some sites use available info (like name), and others just do dummy stuff like Heroku-style... I personally, as a user, don't really like it when my actual name/email is by default my username, from a privacy perspective. But I may be in the minority here. The other benefit to a standard style across different providers is if they enable two kinds of external auth in the future, then they will have a uniform username format out of the box. But it is a good thing to think about.

@Martinsos any preferences on animal vs real name for the Google default username?

All good for me!

Is that, whatever we prefer? :D or a specific option lol you were supposed to tie break haha jk

Hah sorry, but I really think any choice is good here so I am sure you can figure it out :D. Or ok to tie break: if it is not clear that change is better, best to leave it as it is!

waspc/src/Wasp/Util.hs

waspc/src/Wasp/Generator/WebAppGenerator.hs

waspc/src/Wasp/Generator/ServerGenerator/AuthG.hs

waspc/src/Wasp/AppSpec/Valid.hs

Martinsos

@shayneczyzewski awesome, a lot of very nice work, and it is a big step forward!
Looks good to me! I will let @sodic finalize the review, but you have a green light from my side.

waspc/ChangeLog.md

waspc/data/Generator/templates/react-app/src/auth/pages/OAuthCodeExchange.js

waspc/data/Generator/templates/server/src/core/auth.js

Martinsos · 2022-09-05T15:50:43Z

waspc/data/Generator/templates/server/src/core/auth.js

+      username: { in: potentialUsernames },
+    }
+  })
+  const takenUsernames = users.map(user => user.username)


I believe you can do this filtering at Prisma level, with select or smth like that, so we maybe save some data transfer.

You mean just selecting the username col, instead of returning the whole object? Yeah, we could. At max we will have just 10 results though, so I am not sure it would be a huge gain.

Martinsos · 2022-09-05T17:31:20Z

waspc/src/Wasp/Generator/DockerGenerator.hs

  return $
    createTemplateFileDraft
      ([relfile|Dockerfile|] :: Path' (Rel ProjectRootDir) File')
      ([relfile|Dockerfile|] :: Path' (Rel TemplatesDir) File')
      ( Just $
          object
-            [ "usingPrisma" .= not (null $ AS.getDecls @AS.Entity.Entity spec)
+            [ "usingPrisma" .= not (null $ AS.getDecls @AS.Entity.Entity spec),
+              "nodeMajorVersion" .= show (SV.major latestMajorNodeVersion),


How did this become part of this PR, because you learned about this on the way? NO problem with it, just checking that you did not commit this by accident!

It was discovered during the development of this feature and I just decided to fix it during since I was already in this file.

waspc/src/Wasp/Generator/ServerGenerator.hs

waspc/src/Wasp/Generator/ServerGenerator/AuthG.hs

Martinsos · 2022-09-05T17:37:34Z

web/docs/language/features.md

@@ -686,9 +688,13 @@ app MyApp {
 #### `userEntity: entity` (required)
 Entity which represents the user (sometimes also referred to as *Principal*).

-#### `methods: [AuthMethod]` (required)
+#### `externalAuthAssociationEntity: entity` (optional)
+Entity which associates a user with some external authentication provider. We currently offer support for [Google](#google).


Aha, so they pick an entity they want to use? What would it typically be, can it be User again?

Yeah, it follows the same convention we use for User. It cannot be User itself, as it needs a many-to-one relationship to User. I don't think we would want to do it under the covers since if we add/remove an entity as they enable/disable it, they will potentially lose the table data when they disabled it (possibly by accident). I think keeping it explicit is the way to go, and they can decorate it with additional fields/info.

web/docs/language/features.md

shayneczyzewski · 2022-09-05T18:24:45Z

Thanks so much for the review and comments @Martinsos and @sodic They were helpful. We are super close. I got most of the tiny ones included already (and resolved some as I went). The last major thing is to rename externalAuthAssociationEntity to externalAuthEntity. I will do that in a bit, and try to finalize any other lingering suggestions. Should be finalized by tomorrow and then I'll merge. Thanks!

Martinsos · 2022-09-05T20:22:57Z

@shayneczyzewski great, all good for me, feel free to resolve all of my comments any way you see fit.

waspc/data/Generator/templates/react-app/src/auth/pages/OAuthCodeExchange.js

sodic · 2022-09-06T07:59:49Z

waspc/data/Generator/templates/server/src/routes/auth/passport/google/google.js

+import { configFn, getUserFieldsFn } from './googleConfig.js'
+
+// Validates the provided config function returns all required data.
+const config = ((config) => {


What if this function throws an exception. Who can catch it?

Good question. In this case, it will die. But we really don't have a way to recover here, since we need that config. So we could either:

leave as is, let it blow up, and hope the stack trace points them to the problem in their code, or

catch it, make an error message, and they would still need to find their problem and fix it

I slightly lead toward the first (current) only because it should help them find the issue more easily. But this is a good thing to think about in general - if we have user-defined code errors, and we cannot recover, do we just let it blow up or catch and provide a "better" error message in some way?

shayneczyzewski commented Jul 18, 2022

View reviewed changes

waspc/data/Generator/templates/react-app/src/auth/buttons/Google.js Outdated Show resolved Hide resolved

shayneczyzewski commented Jul 18, 2022

View reviewed changes

waspc/data/Generator/templates/react-app/src/auth/useAuth.js Outdated Show resolved Hide resolved

shayneczyzewski commented Jul 18, 2022

View reviewed changes

waspc/examples/todoApp/todoApp.wasp Outdated Show resolved Hide resolved

shayneczyzewski commented Jul 18, 2022

View reviewed changes

waspc/examples/todoApp/todoApp.wasp Show resolved Hide resolved

shayneczyzewski commented Jul 18, 2022

View reviewed changes

waspc/src/Wasp/Generator/Common.hs Outdated Show resolved Hide resolved

shayneczyzewski changed the title ~~DRAFT: Adds Google as an Authentication method~~ Adds Google as an Authentication method Jul 19, 2022

shayneczyzewski marked this pull request as ready for review July 19, 2022 01:40

shayneczyzewski requested review from Martinsos and sodic July 19, 2022 01:40

Martinsos reviewed Jul 19, 2022

View reviewed changes

shayneczyzewski commented Jul 19, 2022

View reviewed changes

Martinsos reviewed Jul 20, 2022

View reviewed changes

shayneczyzewski force-pushed the shayne-jwt-authn-google branch 2 times, most recently from 8d24790 to 562ef0b Compare July 20, 2022 19:10

shayneczyzewski commented Jul 20, 2022

View reviewed changes

Martinsos approved these changes Jul 21, 2022

View reviewed changes

shayneczyzewski added 13 commits August 15, 2022 10:15

POC working, hacky

5229053

signing in with google via otp token

426d4c6

minor update

bb8010f

Refactoring to use some code from shayne-google-authn

5b553eb

refactoring

3422c3c

starting some cleanup

105b493

start of refactor

62496be

more cleanup

3850d44

more tweaks

2ddebff

more cleanup

37bd0cd

update scope url and values

ed6e80e

crossing off some todos

97dd4a8

getting rid of route path helpers for now

2ede79d

clean up google page

f7cdcd4

shayneczyzewski self-assigned this Aug 31, 2022

shayneczyzewski added 2 commits August 31, 2022 11:21

updating some docs

a5121ff

some cleanup

6cf621e

shayneczyzewski commented Aug 31, 2022

View reviewed changes

shayneczyzewski added 6 commits August 31, 2022 13:26

more cleanup

99ca0d3

include patches in final exe

35a8327

rename getUserFields

d896510

Merge branch 'main' into shayne-jwt-authn-google

ede9a70

await configFn just in case user defines an async one

408856a

disable Google auth by default in todoApp

3b97481

shayneczyzewski commented Sep 1, 2022

View reviewed changes

shayneczyzewski changed the title ~~Draft: Adds Google as an Authentication method~~ Adds Google as an Authentication method Sep 1, 2022

shayneczyzewski marked this pull request as ready for review September 1, 2022 15:25

sodic approved these changes Sep 5, 2022

View reviewed changes

shayneczyzewski added 2 commits September 5, 2022 10:26

updates after Filip call

2f7e14e

more PR feedback

55323db

Martinsos approved these changes Sep 5, 2022

View reviewed changes

shayneczyzewski added 3 commits September 5, 2022 14:30

some small PR updates

54fdb42

rename externalAuthAssociationEntity to externalAuthEntity

da3174b

fix warning for unused import

aad6ad2

sodic reviewed Sep 6, 2022

View reviewed changes

waspc/data/Generator/templates/react-app/src/auth/pages/OAuthCodeExchange.js Outdated Show resolved Hide resolved

sodic reviewed Sep 6, 2022

View reviewed changes

shayneczyzewski added 2 commits September 6, 2022 10:10

clean up useEffect

ce1dccb

remove google from bottom auth example

ba9091e

shayneczyzewski merged commit 6cd38b0 into main Sep 6, 2022

shayneczyzewski deleted the shayne-jwt-authn-google branch September 6, 2022 18:36

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Adds Google as an Authentication method #669

Adds Google as an Authentication method #669

shayneczyzewski commented Jul 14, 2022 •

edited

Loading

Martinsos left a comment

shayneczyzewski left a comment

Martinsos commented Jul 20, 2022

Martinsos left a comment

shayneczyzewski left a comment

Martinsos left a comment

Martinsos Jul 21, 2022

shayneczyzewski Jul 21, 2022

sodic Sep 5, 2022

shayneczyzewski Sep 5, 2022

Martinsos Sep 5, 2022

shayneczyzewski Aug 31, 2022

Martinsos Sep 5, 2022

shayneczyzewski Sep 5, 2022

shayneczyzewski Sep 1, 2022

shayneczyzewski commented Sep 1, 2022

sodic left a comment

sodic Sep 2, 2022

shayneczyzewski Sep 5, 2022

Martinsos Sep 5, 2022

shayneczyzewski Sep 5, 2022

Martinsos Sep 5, 2022

Martinsos left a comment

Martinsos Sep 5, 2022

shayneczyzewski Sep 5, 2022

Martinsos Sep 5, 2022

shayneczyzewski Sep 5, 2022

Martinsos Sep 5, 2022

shayneczyzewski Sep 5, 2022

shayneczyzewski commented Sep 5, 2022

Martinsos commented Sep 5, 2022

sodic Sep 6, 2022

shayneczyzewski Sep 6, 2022

		@@ -0,0 +1,26 @@
		import { upsertUserWithRandomPassword } from '../../../../core/auth.js'

		// Default implementation if there is no `auth.methods.google.configFn`.

Adds Google as an Authentication method #669

Adds Google as an Authentication method #669

Conversation

shayneczyzewski commented Jul 14, 2022 • edited Loading

Description

Demo

Syntax

OAuth Flow

Notes

Type of change

Martinsos left a comment

Choose a reason for hiding this comment

shayneczyzewski left a comment

Choose a reason for hiding this comment

Martinsos commented Jul 20, 2022

Martinsos left a comment

Choose a reason for hiding this comment

shayneczyzewski left a comment

Choose a reason for hiding this comment

Martinsos left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

shayneczyzewski commented Sep 1, 2022

sodic left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Martinsos left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

shayneczyzewski commented Sep 5, 2022

Martinsos commented Sep 5, 2022

Choose a reason for hiding this comment

Choose a reason for hiding this comment

shayneczyzewski commented Jul 14, 2022 •

edited

Loading