Skip to content

Latest commit

 

History

History
90 lines (62 loc) · 3.18 KB

README.md

File metadata and controls

90 lines (62 loc) · 3.18 KB
Raw

todos-express-google

This app illustrates how to use Passport with Express to sign users in with Google. Use this example as a starting point for your own web applications.

Quick Start

To run this app, clone the repository and install dependencies:

$ git clone https://github.com/passport/todos-express-google.git
$ cd todos-express-google
$ npm install

This app requires OAuth 2.0 credentials from Google, which can be obtained by setting up a project in Google API console. The redirect URI of the OAuth client should be set to 'http://localhost:3000/oauth2/redirect/google'.

Once credentials have been obtained, create a .env file and add the following environment variables:

GOOGLE_CLIENT_ID=__INSERT_CLIENT_ID_HERE__
GOOGLE_CLIENT_SECRET=__INSERT_CLIENT_SECRET_HERE__

Start the server.

$ npm start

Navigate to http://localhost:3000.

Tutorial

Follow along with the step-by-step Sign In with Google Tutorial to learn how this app was built.

Overview

This app illustrates how to build a todo app with sign in functionality using Express, Passport, and the passport-google-oidc strategy.

This app is a traditional web application, in which application logic and data persistence resides on the server. HTML pages and forms are rendered by the server and client-side JavaScript is not utilized (or kept to a minimum).

This app is built using the Express web framework. Data is persisted to a SQLite database. HTML pages are rendered using EJS templates, and are styled using vanilla CSS.

When a user first arrives at this app, they are prompted to sign in. To sign in, the user is redirected to Google using OpenID Connect. Once authenticated, a login session is established and maintained between the server and the user's browser with a cookie.

After signing in, the user can view, create, and edit todo items. Interaction occurs by clicking links and submitting forms, which trigger HTTP requests. The browser automatically includes the cookie set during login with each of these requests.

When the server receives a request, it authenticates the cookie and restores the login session, thus authenticating the user. It then accesses or stores records in the database associated with the authenticated user.

Next Steps

  • Add additional social login providers.

    Study todos-express-social to learn how to add multiple providers, giving users the choice of which social network account to use when signing in.

  • Add passwordless.

    Study todos-express-webauthn to learn how to let users sign in with biometrics or a security key.

License

The Unlicense

Credit

Created by Jared Hanson