Synchronizing a local user table with an OIDC identity provider

Fri, 18 Sep 2026 08:28:42 +0900

Applications authenticating via OIDC might not need a local user table at all; the session can simply hold whatever claims the identity provider hands back for the user currently logged in. The trouble starts as soon as the application needs to display data about users other than the one currently logged in, for example a list of items with the name of their owner. Other tables can only reference a user by an identifier such as sub, and the OIDC flow only ever hands back claims for whoever is logging in at that moment, so there is no way to look up another user’s name without keeping a local copy of it. This article shows a pattern for solving this in a Nuxt application using nuxt-auth-utils and Drizzle ORM, where a minimal local copy of each user is upserted into a PostgreSQL table on every successful login.

OIDC on Maxime Moreillon

Synchronizing a local user table with an OIDC identity provider