Relationships
#4217 Reads other than findById still treat a lapsed temporary ban as active until the operative next signs in
Opened by stack72 · 10/31/2026
From swamp-club#4194, which makes findById, findByUsername and findBannedIds honour banExpires. These reads still filter on the banned flag alone: username search, email and username lookups and listAdminUsers in better-auth-operative-queries.ts, resolveUsername in oauth-queries.ts (used by routes/api/auth/resolve-user.ts and the admin proxy), member reads in better-auth-collective-queries.ts, the aggregation in mongo-extension-repository.ts, and bannedUsernames in lib/app/repos.ts. After a temporary ban lapses, the operative's key works but they stay hidden on these surfaces until their next browser sign-in. Expected: these reads apply the same not-actively-banned rule.
Open
No activity in this phase yet.
system commented 10/31/2026, 3:29:51 AM
Classified automatically when this issue was filed.
- Source: Swamp Club
If you feel this classification is incorrect, add a ripple to tell us so.
Sign in to post a ripple.