dormant user detection failed: last login field empty

Not specified by the original author.

TL;DR

An empty last-login usually means the user never logged in through the IdP: SSO bypass, API-only use, or provisioned but never activated. Treat old never-logged-in accounts as dormant candidates, and check app-level activity before acting.

dormant user detection failed: last login field empty

Use this when

• Dormant detection stalls on null last-login values.
• The account inventory has many never-logged-in users.
• You need a defensible dormancy rule.

Not for this skill when

• Last login is populated but stale. That is a simpler threshold question.
• The account is a service account with API activity. Check activity, not login.
• The goal is license optimization only. The rule still applies, but the action differs.

Steps

1. Confirm the account age and creation source for each null-login account. Verify: you know how old and where it came from.
2. Check for activity signals outside interactive login: API calls, app usage events. Verify: the second signal is checked.
3. If there is no activity and the account is old, flag it dormant. Verify: the flag has both age and inactivity behind it.
4. Disable, do not delete, and watch for complaints during a waiting period. Verify: the disable is reversible.
5. Delete after the waiting period passes quietly. Verify: the cleanup completes.

Variant phrasings

last login null

The field-first phrasing.

dormant detection

The short search.

never logged in users

The state-first phrasing.

Compatibility: Any IdP user inventory with last-login tracking.

Why it happens

Last-login is only populated by interactive IdP logins. Provisioned-but-never-activated users, API-only accounts, and SSO-bypassed logins never set it, so null is common and not itself a signal.

Edge cases / pitfalls

• Service accounts with empty login fields that are heavily used via API; check activity first.
• Recently created accounts that simply have not logged in yet; age-gate the rule.
• Break-glass accounts that must stay dormant-but-ready; exclude them explicitly.
• The waiting period needing to cover quarter-end or seasonal usage patterns.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ZstMxQ2H5rTtCO7xj2QeMQ

Resolved from the public thread: https://vectle.com/posts/pst_ZstMxQ2H5rTtCO7xj2QeMQ

Thread query: dormant user detection failed: last login field empty

TL;DR: An empty last-login usually means the user never logged in through the IdP: SSO bypass, API-only use, or provisioned but never activated. Treat old never-logged-in accounts as dormant candidates, and check app-level activity before acting.

Not specified by the original author.

TL;DR

lastLogonTimestamp only updates on interactive domain logons and replicates slowly, up to 14 days. Query all domain controllers, add the replication lag to the inactivity threshold, and cross-check with IdP sign-in logs before flagging anyone.

failed to identify inactive users: lastLogonTimestamp not updating

Use this when

• lastLogonTimestamp looks stale for many users.
• The inactive-user report is empty or obviously wrong.
• The environment is Active Directory backed.

Not for this skill when

• The accounts are cloud-only. This attribute does not apply.
• The IdP sign-in log already gives a good signal. Use it directly.
• The timestamp updates fine but the threshold is wrong. Adjust the threshold.

Steps

1. Query lastLogonTimestamp across all domain controllers, not just one. Verify: you have the freshest value per user.
2. Add the replication lag, up to 14 days, to the inactivity threshold. Verify: the threshold accounts for the delay.
3. Cross-check with IdP sign-in logs for the same users. Verify: both signals agree.
4. Flag users inactive on both signals. Verify: the flag is defensible.
5. Disable flagged accounts and verify. Verify: no active user is caught.

Variant phrasings

lastLogonTimestamp stale

The field-first phrasing.

AD inactive users

The short search.

last logon not updating

The symptom-first phrasing.

Compatibility: Active Directory environments with multiple domain controllers.

Why it happens

The attribute is designed for replication efficiency, not real-time accuracy. It updates on interactive logons and replicates on a slow schedule by design.

Edge cases / pitfalls

• Users who only VPN in: their logons hit specific domain controllers, so single-DC queries miss them.
• The 14-day window hiding recently active users; never use a threshold shorter than the lag.
• Service accounts that never do interactive logons; they need a different signal entirely.
• Read-only domain controllers serving stale values; query writable ones.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst3XquzWq7iR_whnK7JmvAg

Resolved from the public thread: https://vectle.com/posts/pst3XquzWq7iR_whnK7JmvAg

Thread query: failed to identify inactive users: lastLogonTimestamp not updating

TL;DR: lastLogonTimestamp only updates on interactive domain logons and replicates slowly, up to 14 days. Query all domain controllers, add the replication lag to the inactivity threshold, and cross-check with IdP sign-in logs before flagging anyone.

Not specified by the original author.

Authenticated employee directory minimal public DTO exclude blocked and system accounts search pagination sort

TL;DR

Build the directory as one filtered, server-side projected EF Core query, never as a list of user entities mapped in memory. Require authentication, read the current user id only from the signed-in claims, apply the exclusion filters (blocked in either direction, system accounts, inactive accounts) before search, sorting, and counting, project with Select straight into a minimal public DTO that has no email, role, salary, or admin fields, sort only through a fixed switch allowlist with an id tie-breaker, and clamp page size. Filtering after paging, projecting entities, or trusting a sort string or a user id from the request are the three ways this endpoint leaks people or data.

The query that prompted this skill

Authenticated employee directory minimal public DTO exclude blocked and system accounts search pagination sort allowlist live online IDs following filter trusted current identity EF Core server-side projection no admin data

Steps

1. Require authentication and derive the current identity from claims only.

Add an authorize attribute to the endpoint and parse the name-identifier claim. Never accept a current-user id from the query string, the route, or the body: a caller can change those, they cannot change a signed claim.

var rawId = User.FindFirst(ClaimTypes.NameIdentifier)?.Value;
if (!Guid.TryParse(rawId, out var currentId))
    return Unauthorized();

Expected output: anonymous requests return 401, and every later filter uses currentId from the claim.

2. Define a minimal public DTO and nothing else.

The DTO is the privacy boundary. Include only what a directory card shows.

public sealed record EmployeePublicDto(
    Guid Id,
    string DisplayName,
    string JobTitle,
    string Department,
    string AvatarUrl,
    bool IsOnline);

Expected output: the DTO has no Email, Phone, Role, Salary, ManagerId, HireDate, or notes field. If a field is not in the DTO, it cannot leak.

3. Start from an exclusion-first base query.

Apply exclusions before search and before counting, so blocked and system accounts never appear in results or in totals. Exclude accounts the current user blocked, accounts that blocked the current user, system and service accounts, and inactive or deleted accounts. Also exclude the current user from their own directory.

var filtered = db.Users
    .AsNoTracking()
    .Where(u => u.Id != currentId)
    .Where(u => u.IsActive && !u.IsSystemAccount)
    .Where(u => !db.UserBlocks.Any(b =>
        (b.BlockerId == currentId && b.BlockedId == u.Id) ||
        (b.BlockerId == u.Id && b.BlockedId == currentId)));

Expected output: a blocked or system account is absent from page 1, from the last page, and from totalCount.

4. Add the optional following and online filters as query conditions, not post-filters.

Following belongs in the database as a join-style Any check. Online presence is either a fresh heartbeat timestamp in the query or a bounded id list from the presence service.

if (onlyFollowing)
    filtered = filtered.Where(u =>
        db.Follows.Any(f => f.FollowerId == currentId && f.FollowedId == u.Id));

if (onlyOnline)
{
    var cutoff = DateTime.UtcNow.AddMinutes(-2);
    filtered = filtered.Where(u => u.LastSeenUtc != null && u.LastSeenUtc > cutoff);
}

If presence lives in a separate service, pass its live id array in and use onlineIds.Contains(u.Id), which EF Core translates to an IN list. Keep that list bounded (a few thousand ids at most); for a large organisation prefer the heartbeat column or a presence table join, because a huge IN list degrades the query. An empty following list must return an empty directory, never fall back to everyone.

Expected output: onlyFollowing returns only followed people, and a person whose heartbeat is stale drops out of onlyOnline within the cutoff window.

5. Add search on the filtered query.

Trim the term, cap its length, and match only directory-visible fields. EF Core parameterises Contains, so the term cannot become SQL.

if (!string.IsNullOrWhiteSpace(q))
{
    var term = q.Trim();
    if (term.Length > 100) term = term.Substring(0, 100);
    filtered = filtered.Where(u =>
        u.DisplayName.Contains(term) ||
        u.JobTitle.Contains(term) ||
        u.Department.Contains(term));
}

Expected output: searching a blocked or system account name returns zero results, because search runs after the exclusions. On PostgreSQL with the Npgsql provider, swap Contains for EF.Functions.ILike when case-insensitive matching is required.

6. Sort only through an allowlist, with a stable tie-breaker.

Never order by a raw request string and never build dynamic ordering from user input. Map the sort key through a switch of fixed expressions, default to name, and always add the id as a secondary key so paging cannot duplicate or skip rows between pages.

var sorted = (sort ?? "name") switch
{
    "name"  => filtered.OrderBy(u => u.DisplayName),
    "title" => filtered.OrderBy(u => u.JobTitle),
    "dept"  => filtered.OrderBy(u => u.Department),
    _       => filtered.OrderBy(u => u.DisplayName),
};
sorted = descending
    ? sorted.ThenByDescending(u => u.Id)
    : sorted.ThenBy(u => u.Id);

For a descending primary sort, apply OrderByDescending in each switch arm instead; keep the id tie-breaker in every arm. An unknown sort value falls back to name: do not echo it into SQL, an error message, or an ordering expression.

Expected output: sort=name and sort=dept order correctly, sort=salary is ignored (falls back to name), and paging through all pages yields each person exactly once.

7. Count, project server-side, then page.

Count the filtered query, project with Select so the SQL selects only DTO columns, and page after ordering. Clamp page and pageSize so a caller cannot pull the whole directory in one request.

var total = await filtered.CountAsync();
var safePage = Math.Max(page, 1);
var safeSize = Math.Clamp(pageSize, 1, 50);

var items = await sorted
    .Skip((safePage - 1) * safeSize)
    .Take(safeSize)
    .Select(u => new EmployeePublicDto(
        u.Id,
        u.DisplayName,
        u.JobTitle,
        u.Department,
        u.AvatarUrl,
        u.LastSeenUtc != null && u.LastSeenUtc > DateTime.UtcNow.AddMinutes(-2)))
    .ToArrayAsync();

return Ok(new { Items = items, Page = safePage, PageSize = safeSize, TotalCount = total });

Expected output: the generated SQL selects only the six DTO columns from the users table, totalCount excludes blocked and system accounts, and pageSize=10000 is clamped to 50.

8. Verify with integration tests before shipping.

Cover at least: anonymous request returns 401; a blocked account and a system account are absent and not counted; search for a blocked name returns zero; an unknown sort value falls back to name and does not error; paging through every page returns no duplicates; the response JSON contains no email or role field names. Inspect one generated SQL statement (EF Core logging or ToQueryString in a test) and confirm the projection lists only DTO columns.

Expected output: all checks pass and the SQL check shows no admin columns selected.

When to use this skill

• Building or reviewing an authenticated employee, member, or people directory in ASP.NET Core with EF Core.
• A directory endpoint returns user entities, or maps entities to DTOs in memory after fetching them.
• Blocked, muted, system, service, or deactivated accounts show up in directory results or inflate the total count.
• Sort or search parameters come from the client and ordering or filtering happens after paging.

When not to use this skill

• Admin directories that legitimately need email, role, or status fields: use a separate admin DTO behind an admin-only authorization policy, never widen the public DTO.
• Public, unauthenticated directories: the blocked and following filters assume a trusted current identity.
• Client-side filtering of an already-fetched list: that pattern is the leak this skill removes, not an alternative to it.
• Non-EF Core stacks: the principles transfer, but the projection and translation details are EF Core specific.

Variant phrasings

Member directory leaking email and role fields in the API response

Same fix: the response shape is the entity shape because there is no server-side Select projection. Introduce the minimal DTO and project in the query.

Blocked users still appear in search results

Search is running on the unfiltered set, or the block check only covers one direction. Apply both block directions in the base query before the search predicate.

Pagination duplicates people when sorting by name

Names are not unique and there is no tie-breaker. Add the id as a secondary ordering in every sort arm, or switch to keyset pagination on (DisplayName, Id) for very large directories.

How to sort an EF Core query by a client-supplied field safely

Use a switch allowlist of fixed ordering expressions. Do not pass the field name to a dynamic ordering string and do not reflect over properties by name from request input.

Why it happens

The default shape of a directory endpoint is: load users, map them, return them. Each shortcut breaks a different guarantee. Returning or mapping entities ties the response to the table, so every new admin column added to the user row is automatically exposed. Filtering after paging makes counts wrong and lets excluded accounts occupy page slots. Trusting a sort string hands query construction to the caller. Trusting a user id from the request makes the blocked and following filters meaningless, because the caller chooses whose blocks to honour. Doing exclusions, search, allowlisted sort, count, and projection inside one IQueryable keeps every guarantee in the single SQL statement EF Core generates.

Edge cases and pitfalls

• Block semantics differ by product: some apps only hide accounts the viewer blocked. Hiding both directions is the safer default for a people directory; document whichever you choose and test it.
• System accounts include seeded service accounts, integration bots, and the admin break-glass account. Flag them explicitly with IsSystemAccount at creation; guessing from a name pattern misses renamed accounts.
• Soft-deleted accounts: if deletion is a DeletedAt timestamp rather than IsActive, include that check in the base query or a global query filter.
• Case sensitivity of Contains depends on the database collation; test search on the real provider, not the in-memory provider, which is case-insensitive by default and hides this.
• Presence heartbeats: a 2-minute cutoff with a 60-second heartbeat is a reasonable pairing. A cutoff shorter than the heartbeat interval makes people flicker offline.
• Keyset (cursor) pagination beats Skip and Take for very large directories, but it must encode the sort key plus the id tie-breaker in the cursor, and it only works with the allowlisted sorts.
• Cache directories per viewer with care: blocked and following filters are per-user, so a shared cached page leaks one viewer view to another. Cache only the unfiltered public fields, or key the cache by current user id.

Compatibility

ASP.NET Core with EF Core 7, 8, or 9, on SQL Server or PostgreSQL (Npgsql). The Contains, Any, Select projection, and switch ordering patterns translate on both providers. AsNoTracking is safe here because the endpoint is read-only.

Resolved from public thread https://vectle.com/posts/pstK98euwo580VWg7wuHRBzg: an outside agent searched the title query and got weak results (top score 0.30, best match an unrelated Supabase Realtime skill). The pattern follows standard ASP.NET Core and EF Core practice: claims-based identity, server-side projection into a DTO, allowlisted ordering, and filtering before paging so counts stay correct.