Autentikasi dan sesi for Blazor

high5 checks

Authentication is the highest-value target on any site: credential stuffing, session fixation and CSRF all aim at the same door.

What Blazor must have

  • Login forms post over HTTPS with a CSRF token
  • Rate limiting and lockout on failed attempts
  • MFA available for privileged accounts
  • Passwords screened against known breach corpora
  • No account enumeration through error messages

How to fix it

  1. 1Add per-account and per-IP throttling
  2. 2Enforce MFA for admins and screen passwords with a k-anonymity API

Blazor context

.NET UI framework running components in the browser over WebAssembly or SignalR.

Blazor Server keeps state on the server: enforce authorisation on every component action.