Eliminating Database Lookups with Auth0 Custom Claims
How to enrich JWT tokens with user data during login, eliminating per-request database lookups while keeping your domain logic decoupled from your identity provider.
I write about software engineering: distributed systems, cloud platforms, mobile development, AI-augmented workflows, and the decisions that matter when you are building for production. Twenty years of building software means I have opinions, and this is where they go.
How to enrich JWT tokens with user data during login, eliminating per-request database lookups while keeping your domain logic decoupled from your identity provider.
HTTP already has error semantics. RFC 9457 Problem Details gives your error payloads a standard structure to match. Here's why it matters and how to implement it in ASP.NET Web API using middleware.
Everyday kit is not just for gear people. Here's my current AI development workflow, an honest account of what it replaced, and why I'm already working on the next version.
Auth0 Universal Login puts all your users on a shared auth0.com subdomain. That breaks password manager autofill and credential association on iOS and Android. A custom domain fixes it, and it's easier to configure than you'd expect.
Attrakto started as a fidget with two bottle caps and became a calm daily puzzle game. Here is how it got here.
An Azure App Service Key Vault reference without a trailing slash silently returned an older version of my secret after I rotated it. Token validation failed because the issuer URL no longer matched. Here's what happened, what the documentation actually says, and why the slash matters.