When to Customize Passport’s serializeUser and deserializeUser Callbacks
Learn how Passport’s serializeUser and deserializeUser callbacks control what lives in the session and how to add a caching layer to avoid costly DB lookups on every request.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how Passport’s serializeUser and deserializeUser callbacks control what lives in the session and how to add a caching layer to avoid costly DB lookups on every request.
Learn how to configure Passport.js LocalStrategy to work with custom login field names while keeping authentication secure.
Scattered Authorization headers and repeated 401 handling create fragile code. Using axios request and response interceptors on a custom instance centralizes token attachment and single‑refresh retry logic, with ordering caveats and verification steps.
Deploying JupyterHub with OAuth2 requires a secure, minimal design that delegates identity verification, enforces TLS, and isolates notebook servers. This guide details requirements, trust boundaries, operational checks, failure modes, and a practical verification checklist.
Architecture note for WordPress REST API application‑password authentication: requirements, minimal design, trust boundaries, operational checks, failure modes, and verification steps.
Learn how to separate authentication from session persistence using Passport.js and the Local Strategy to build secure, scalable Node.js user sessions.
Guide to choosing Teleport auth method: compare local, OIDC, SAML; show GitHub OIDC setup and verification steps.
Learn how to implement OAuth 2.0 with PKCE to secure public clients like SPAs and mobile apps, eliminating the need for insecure client secrets.
Shows how to configure Passport.js with the Local strategy, keep session data minimal, define trust boundaries, and add operational checks for secure Node.js authentication.