← All articles

Reading-path month: January 2026. Collection published on September 12, 2026. Months organize the reading path; they are not earlier publication dates.

Authentication: design beyond login

Device changes and recovery also establish trust.

Identity

Content produced with AI assistance for Thiago Silva’s website. Independent editorial analysis; it does not represent clients or employers.

Reading context

A short architecture article. The technical reference supports the topic; hypothetical scenarios and assessment proposals are editorial analysis, not accounts of personal implementations.

Original source ↗

The architecture decision

A login screen is only one account entry point. Registration, recovery and contact changes also affect who controls an identity. Reviewing them separately can create inconsistent rules.

Practical application

Consider a hypothetical journey with strong login but an email change relying on an old session. Editorial proposal: map every identity change to its trigger, required evidence and account-holder notification.

How to verify

Before release, simulate device loss and a legitimate phone change. Record both barriers and support shortcuts. Assess security and usability together, especially when recovery becomes the easiest route to account takeover.

Sources

  1. OWASP — Authentication Cheat Sheet