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.
Software Engineer
I build software. I have been at it for twenty years, across cloud platforms, distributed systems, mobile apps, and AI-augmented engineering. For clients, that has meant greenfield development, legacy modernization, and shipping software faster. For myself, it means products like Attrakto, live on the App Store, with more in development. If you need something built and want a senior engineer who will personally own it from start to finish, I can do that.
I have been building in Colorado since 2006. Before that, I studied digital art and telecommunications at University of Louisiana at Lafayette, which turned out to be a more useful path than it sounds. Twenty years later, I am still here, still building, and still showing up every two weeks for the same tabletop RPG group I started with back then.
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.