Google Login in Express with PassportJS & JWT
The article provides a guide on implementing Google Authentication in an Express.js application using various technologies. It outlines the necessary steps, including setting up Google OAuth credentials and configuring PassportJS for authentication. Additionally, it details the required changes to the user model and the creation of routes for handling Google login.
- ▪The implementation uses TypeScript, Express.js, Mongoose, Passport.js, and JWT for authentication.
- ▪Users must create OAuth credentials in the Google Cloud Console to obtain a Client ID and Client Secret.
- ▪The user model needs to include fields for refreshToken and googleId, and password login should be made optional.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/nhero/google-login-in-express-with-passportjs-jwt-1483 |
| Publication time | Sat, 23 May 2026 10:12:28 +0000 |
| Retrieval time | 2026-05-23T10:37:26.419Z |
| Last seen | 2026-05-23T10:37:26.419Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | dY6KUb3N6Fiq |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 2071314) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } NHero Posted on May 23 • Originally published at nhero.me Google Login in Express with PassportJS & JWT #webdev #backend #express #passportjs In this blog, we will implement Google Authentication in an Express.js app using: TypeScript Express.js Mongoose Passport.js JWT Authentication Project Structure └── src/ ├── config/ ├── controllers/ ├── middlewares/ ├── models/ ├── routes/ ├── utils/ ├── app.ts └── index.ts ├── .env ├── package.json └── tsconfig.json Enter fullscreen mode…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
