Loading
Pick a focused question that fits your time, stack, and interview goal.
10 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 API keys, client credentials, managed identity, mTLS, scopes, rotation, and per-client observability.
Explains short-lived access tokens, refresh-token rotation, revocation, storage choices, and replay detection.
Explains reset-token generation, hashing, expiration, generic responses, session revocation, and abuse controls.
Explains password verification, hashing, throttling, generic errors, lockout, and safe login telemetry.
Explains logout semantics for token-based APIs, revoking refresh tokens, device/session records, and short-lived access-token limits.
Separates OAuth authorization from OpenID Connect authentication and explains why modern interactive clients use authorization code with PKCE.
Explains identity versus permission checks in API request handling and why both boundaries need server-side enforcement.
Explains the boundary between OAuth/OIDC identity, application users, claims mapping, roles, and app-specific permissions.
Explains JWT validation, trusted issuers, audiences, expiration, signing keys, claims, and server-side authorization boundaries.