User Accounts w/ Google login - Githubissues

ucladevx / Bmaps-Backend

Documentation and source code for public events/locations APIs.

http://github.com/ucladevx/Bmaps-Backend/

MIT License

6 stars 2 forks source link

User Accounts w/ Google login #116

Open TrinaKat opened 5 years ago

TrinaKat commented 5 years ago

Currently have basic implementation of Facebook Auth/Login, but due to API limitations might just use Google login instead.

Facebook:

Integrate with Facebook event services (which all require app review)
Potential to expand to support "friend activity" etc.
Use FB profile picture, user data, etc.
Can check if in UCLA group to verify that they are UCLA-affiliated?
Clubs have Facebook pages and eventually can have "Club account" status of some kind

Google:

Use Google profile picture, email, etc.
Must be *ucla.edu email, which means only UCLA-affiliated accounts
Clubs will have to have *ucla.edu email, or we will enforce a case-by-case review of each club that wants to sign up for club (not everyone should have ability to create events)
Increased ease to integrate with MyUCLA?

Next Steps:

Integrate Google auth to site, store user data in database
Make sure user info isn't duplicated, unique key = email?
Ability to update user info through Mappening (add picture, change name, etc.)
Unlocks many more features we can develop! (e.g. favorite events, export to calendar, user-contributed events, recommended events, personalization in general)

TrinaKat commented 5 years ago

Potentially relevant example: https://github.com/GenFirst/angular2-node-fb-login/blob/master/frontend/src/app/login/login.component.ts Google login: https://developers.google.com/identity/sign-in/web/sign-in Mappening Developers Account: https://console.developers.google.com/apis/credentials?authuser=0&project=mappening-193922 (not sure if this link will work for you)

Use database collection g_users on mlab, add backend code for Google login (with UCLA account) under src/mappening/auth/google.py