Simplest Passport/JWT implementation with cookie and bearer authentication support

100%

Simplest Passport/JWT implementation with cookie and bearer authentication support

✓ Published0🌍 Public

Last edited Sep 28, 2017

Created on Sep 28, 2017

This example demonstrates a minimal JSON Web Token (JWT) authentication flow using Passport.js, supporting both HTTP-only signed cookies and bearer tokens in the Authorization header. It shows registration, login, and a protected `/secret` route, with user credentials hashed via bcrypt and tokens signed by `jsonwebtoken`. The code relies on `passport-jwt`’s `ExtractJwt.fromExtractors` to combine a custom cookie extractor with `fromAuthHeaderAsBearerToken`. The in-memory `Users` class stores user data and validates passwords asynchronously, while the server uses Express, `body-parser`, and `cookie-parser` for request handling.

AI-generated description

Similar vizzes

Loading thumbnail…

Express authentication using Redis for session store and Couchdb for database (in coffeescript!)

This example demonstrates user authentication and session management in a CoffeeScript-built Express application, showing how login, signup, and logout routes handle password hashing and session regeneration. The code uses Redis as the session store via `connect-redis` and CouchDB for user persistence through the `couchdb` client, with CSRF protection from `express-csrf` and password salting via `hash.sha1`. The visualization highlights the request flow across these middleware and database calls, including error handling for duplicate users and failed logins, while relying on the Fugue cluster for deployment.

AAnsonT

64% match

Loading thumbnail…

Using Node-Jose to for RSA jwt with key store

This example demonstrates how to sign and verify a JSON Web Token (JWT) using RSA keys managed through the `node-jose` keystore. It generates a fresh RSA 2048-bit key pair, stores it as a JSON keystore file, and then signs a payload with `JWS.createSign` using the `RS256` algorithm. The code also verifies the token with `JWS.createVerify`, converts the JWK to PEM via `jwk-to-pem`, and validates it again with the `jsonwebtoken` library’s `jwt.verify`. The keystore is loaded from or saved to `.cert/keystore.json`.

AAnsonT

63% match

Loading thumbnail…

Gist c2007066af4a2f2b97d4293778f8af5d

This Scala example demonstrates a complete JWT (JSON Web Token) lifecycle, creating a signed token with custom claims and then verifying and decoding it. The code generates an ES256 key pair using `GeneratorKeyFactory` from the Ubirch crypto library, then encodes a token with `Jwt.encode` that includes tenant, device, UUID identifiers, and custom role claims, before decoding it back with `Jwt.decodeRawAll` to display the parsed header, payload, and signature. The visualized output is the `Try` result showing the extracted JSON claims alongside the cryptographic signature.

CCarlos-Augusto

56% match

Loading thumbnail…

Gist d8122161cee20af6219aa00b744ec60e

This example decodes a JSON Web Token (JWT) in Scala, showing the three components of the token: header, payload, and signature. It uses the `pdi.jwt` library to encode a claim with a secret key and the HS256 algorithm, then decodes it back with `Jwt.decodeRawAll`. The payload contains issuer, audience, expiration, and a custom role claim, serialized via `org.json4s`.

CCarlos-Augusto

55% match

Loading thumbnail…

Gist 86a2162840809aa2b4e4890ec2ba7100

This example demonstrates how to create and validate a JSON Web Token (JWT) using the Scala library `pdi.jwt` with ES256 asymmetric encryption. It shows the complete token lifecycle: generating a key pair with `GeneratorKeyFactory` on the `PRIME256V1` curve, encoding claims (including custom fields like `role` and `env`), and finally decoding and verifying the token with the public key. The code serializes claims using `org.json4s` and `jackson.compactJson`, highlighting the interplay between JWT construction, cryptographic signing, and verification.

CCarlos-Augusto

55% match

Loading thumbnail…

Gist ca8ce8dbd8dbba7b501860f3d569f019

This example demonstrates a lightweight Express server that acts as a CORS proxy for a joke API, enabling browser-based requests to bypass cross-origin restrictions. The code uses the `express` and `request` libraries to define a route, `/jokes/random`, which forwards requests to `https://joke-api-strict-cors.appspot.com/jokes/random` and relays the JSON response back to the client. A middleware sets the `Access-Control-Allow-Origin` header to `*`, allowing any frontend to access the proxied data. The server listens on a configurable port, defaulting to 3000, and handles errors by returning a JSON error object. This setup illustrates a simple server-side solution for enabling client-side data fetching from a restricted external source.

115Dkatz

52% match

Loading thumbnail…

express sample and quick examples and descriptions of body, params, and query

This example demonstrates the differences between `req.body`, `req.params`, and `req.query` in ExpressJS, showing how each carries client data to the server. The code pairs ReactJS frontend components with Axios requests against a backend using ExpressJS and body-parser. It illustrates POST/PUT/PATCH requests sending data in `req.body`, GET/DELETE requests embedding values in URL routes via `req.params`, and GET requests appending key-value pairs through `req.query`. The metaphor of a restaurant clarifies the client-server-database relationship.

JJ6K

50% match

Loading thumbnail…

Gist 05471e1965de232f4434a8624c8949dc

This example demonstrates a minimal Express.js server that serves player data from a SQLite database, exposing endpoints for retrieving all players or looking up a single player by email. The backend uses `express`, `body-parser`, and the `sqlite3` library, with an async utility function (`getPlayers` or `getPlayerByEmail`) handling database queries. Although no charting or visualization library is present, the code illustrates a typical API structure for feeding data to a front-end visualization. The root route returns a plain JSON message, while `/players` and `/playerByEmail` respond with JSON arrays or objects, showing how raw data would be delivered for subsequent graphical rendering.

WWill Carter

50% match