What is Authentication?
You'll learn what authentication means and how it differs from authorization.
The Core Idea
Authentication is the process of verifying that someone (or something) is who they claim to be. It answers the question: "Are you really you?"
Think of authentication like showing your ID at airport security. The officer checks your driver's license or passport to confirm your identity matches what you claim. They're not deciding where you can go or what you can do—they're simply verifying you are the person named on that document.
Authentication vs Authorization
These two terms are often confused, but they serve distinct purposes:
- Authentication = "Who are you?" (Identity verification)
- Authorization = "What are you allowed to do?" (Permission checking)
Authentication always comes first. You can't grant someone permissions until you know who they are.
Analogy: Hotel Check-In
When you arrive at a hotel:
- Authentication: You show your ID and reservation confirmation. The front desk verifies you're the person who booked the room.
- Authorization: Once authenticated, they give you a key card that only opens your room and perhaps the gym—not other guests' rooms or staff areas.
Why It Matters
Without proper authentication, systems can't trust user identities. An attacker could claim to be anyone—an administrator, another user, or the system owner—and gain unauthorized access to sensitive data or functionality.
Key Takeaway: Authentication verifies identity ("Who are you?"), while authorization determines permissions ("What can you do?"). Authentication is the essential first step in any secure system.