search

AshleyNWagner / IndieProject

0 stars 0 forks source link

Checkpoint 3 ready for review #7

Open AshleyNWagner opened 2 years ago

AshleyNWagner commented 2 years ago

@pawaitemadisoncollege

The only thing that I've changed since the last checkpoint was setting up Cognito and deploying it on Elastic Beanstalk. I don't really understand how Cognito works with getting users' information into my database, or if the users' information will just be stored in the user pool. Right now, you can still access users' usernames through the search bar, but those are users that are entered in through the sign up page I made before I knew anything about Cognito. If you could shed some light on this, that would be great.

Here is think, if you need it: http://indieproject-env.eba-rut2eisx.us-east-2.elasticbeanstalk.com/

I can't access it at all in Chrome despite trying to force it to let me, but it seemed to work in other browsers.

pawaitemadisoncollege commented 2 years ago

Nice job hitting checkpoint 3 @AshleyNWagner! Regarding how picky Chrome is - I KNOW! I was able to test your application in Safari just fine. For the purposes of Ent Java, this is ok. In the real world, you'd get a real certificate to use, but I didn't want to force you all down that path for this class...

Here's my recommended flow to get user info into your database:

After the user signs in:
   Get the username (we did this in the exercise - when we displayed username back to the jsp)
   Check if the user in your database (use the dao to get user by username)
       If the user is in your database, carry on with whatever action the user wants to take
       If the user is not in your database, add them

Let me know if that helps!