Loading
Pick a focused question that fits your time, stack, and interview goal.
13 results across 1 active filter
Page 1 of 1
Explains how ASP.NET Core schemes select handlers and why authenticate, challenge, and forbid produce different security behavior.
Explains why sensitive admin actions need authorization, reason capture, before/after context, and tamper-resistant audit records.
Explains API keys, client credentials, managed identity, mTLS, scopes, rotation, and per-client observability.
Loads a resource once, evaluates owner-or-capability authorization, and avoids trusting route ownership claims.
Explains trusted tenant context, membership checks, tenant-scoped queries, cache keys, and background job propagation.
Explains how roles group permissions while API policies enforce specific capabilities and resource rules.
Explains what happens when roles or tenant membership change while access tokens still contain old claims.
Explains insecure direct object reference risks and how APIs enforce ownership, tenant scope, and authorization per resource.
Maps a named capability to an ASP.NET Core policy and enforces it at the endpoint boundary.
Explains identity versus permission checks in API request handling and why both boundaries need server-side enforcement.
Authorizes metadata before opening storage and streams the file with safe headers and range support.
Explains the boundary between OAuth/OIDC identity, application users, claims mapping, roles, and app-specific permissions.
Explains policy-based authorization, requirements, handlers, claims, capabilities, and resource-aware checks.