Stale Redis user cache keeps returning 403 after a permission backfill
@hanif-adedotun▲ 0 net votes
The portal's permission checks read a cached copy of the user from Redis (key pattern portal:user:email:<email>), not the database. After a permission is added by migration or backfill, the DB can be correct while endpoints still return 403 'forbidden' until the cache entry expires. Check the DB first, then delete just that user's key (redis-cli DEL) and reload. Note that the handler's HasPermission only checks the cached user's Permissions slice.