Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Authenticate Portal with Backend #1

Open
4 tasks
swghosh opened this issue Dec 9, 2018 · 0 comments
Open
4 tasks

Feature: Authenticate Portal with Backend #1

swghosh opened this issue Dec 9, 2018 · 0 comments
Labels
backend Requires use of PHP and databases. enhancement New feature or request frontend Involves use of HTML, JavaScript code on the client side.

Comments

@swghosh
Copy link
Collaborator

swghosh commented Dec 9, 2018

Background

A simple portal as a part of the website that uses Google Sign In / Login with Facebook to authenticate users.

Facebook Login

Login with Facebook has been implemented on the website using a demo page (File: www/portal/index.php). Which has all the required credentials for the required OAuth authentication*.

Refer: Login with Facebook for Websites

Google Sign In

Google Sign In has also been implemented on the website using the same demo page (File: www/portal/index.php). It allows Google OAuth based Sign in for this website. The OAuth consent screen has also been approved from Google's side.

Refer: Google Sign-In for Websites

Workaround

A simple web portal that can login users with either their Google account or Facebook is required to be implemented. The following steps are required to be programmed in order to bring it to action:

  • Authenticate user credentials with a backend server, both in case of Facebook and Google account sign in success. Kindly refer to these articles: for Google and for Facebook.
  • Create database tables to accordingly store the user data. A common table schema could store the details fetched from the respective login API like name, email address, etc.
  • Show user a welcome screen if he/she is a new user, record his/her personal information to the database
  • Redirect the user to a demo portal like page (which is of course only accessible by the registered users / authenticated members exclusively). Use HTTP status codes like 403 to restrict content access to unauthenticated members or alternatively redirect them with 302 to help them sign in. Refer to these articles wherever required: HTTP Status Codes (MDN), Set Header for Location in PHP.

You are requested to expedite this task.

@swghosh swghosh added enhancement New feature or request frontend Involves use of HTML, JavaScript code on the client side. backend Requires use of PHP and databases. labels Dec 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Requires use of PHP and databases. enhancement New feature or request frontend Involves use of HTML, JavaScript code on the client side.
Projects
None yet
Development

No branches or pull requests

1 participant