Open timowens9 opened 5 years ago
Would we like to have two seperate forms or use the same form with two buttons appended? I'm envisioning a registration form that asks for information including name, location, date of birth, etc. and a sign-in form as a separate form that asks for email or username and password. Alternately, we could just ask for email and password and share forms, and users can then fill out their name, location, etc. on their profile page, perhaps.
Do we want these forms to be overlays, without redirecting the user to another page, or do we want discrete web pages?
Here is what I'm thinking.
For the registration, User can sign-up with their google and facebook account or email.
After registration, user can change their profile picture, bio, and the location in the profile page.
Let me know what you guys are thinking!
Good idea on setting up oauth signing with social media; we should definitely set that up if we can, along with some form of 2 factor authentication - passwords are essentially obsolete these days, after all.
how about something like this Two Factor seems pretty straight forward
Check out https://auth0.com - they are an api that handles all auth for us, so we don't have to worry about implementing our own encryption all over the place. Works with all stacks, can be used front end or back end, has Postman integration, and is easily extensible for our needs, so we can add 2fa at any time later on after setting up a super basic signin handler.
On the other hand, if you want the experience of rolling our own encrypted data pipeline, I'm open to that too!
This looks good to me.
Check out https://auth0.com - they are an api that handles all auth for us, so we don't have to worry about implementing our own encryption all over the place. Works with all stacks, can be used front end or back end, has Postman integration, and is easily extensible for our needs, so we can add 2fa at any time later on after setting up a super basic signin handler.
On the other hand, if you want the experience of rolling our own encrypted data pipeline, I'm open to that too!
I'm down!
An Account Profile could have a listing of upcoming events they've "joined" and some details about these events, like other attendees, date, location, price etc.
Should we have some settings on the profile, for example, notifications and which to allow/reject?
A meetup profile for inspiration/reference
As a new potential user, I want to create and register a new account so I can log in and use the application.
Considerations: User name, email, and password fields, Two buttons, one for sign in and one for register
Testing: Input form validation check db if user exists