MODULE 06 · AUTHENTICATION & SECURITY
Authentication
Authentication is the process of verifying who a user or system is before access is granted.
01 · What is it?
Authentication checks an identity claim against one or more credentials, such as a password, security key, or trusted identity provider.
The result is an answer to “Who is this?” It does not by itself decide which actions that identity may perform.
02 · Think of it like...
Think of authentication like showing identification at a building entrance.
The visitor states who they are, presents a credential, and waits while the entrance system checks it.
A successful check establishes an identity that the rest of the building can use.
Visitor
→
Credential
→
Identity Check
→
Verified Identity
03 · What does it do?
Authentication gives a system a trustworthy identity to use in later access decisions.
Verify IdentityCheck that a user or service controls the claimed credential.
Establish a SessionKeep the verified identity available across related requests.
Issue a TokenCreate a signed or otherwise protected proof for later requests.
Reject ImpostorsStop requests when credentials are missing, invalid, or expired.
04 · Where is it used?
Authentication appears anywhere a system needs to recognize a person, service, or device.
Web ApplicationsAccount sign-inUsers sign in before viewing private pages or personal data.
APIsService identityClients prove which application or service is making a request.
Enterprise SystemsSingle sign-onAn identity provider authenticates employees across connected tools.
DevicesMachine identityA device proves its identity before connecting to a trusted service.
05 · Example
- The user submits an email address and password.
- The server finds the account and compares a password hash.
- If the check succeeds, the server creates a session or token.
- Later requests carry that proof so the server can recognize the user.
The password should be checked against a securely stored hash, not stored as readable text. The session or token should also be protected and expire according to the system’s risk.
Authentication succeeds only when the system can verify the presented credential under its current rules.
06 · How it connects
User
→
Login Form
→
Authentication Service
→
Session / Token
→
Authorization Check
→
Protected Resource
Authentication establishes identity; authorization uses that identity to decide what the request may do.
07 · Do Not Confuse
Authentication
Checks who a user or system is.
Authorization
Checks what that verified identity is allowed to do.
Credential
Is evidence used during authentication, such as a password or security key.
A successful login does not automatically grant access to every resource or action.
08 · Topic Glossary
| ENGLISH TERM | 中文 | SIMPLE ENGLISH | 中文小白理解 |
| Authentication | 身份认证 | Checking who a user or system is. | 检查用户或系统到底是谁。 |
| Identity | 身份 | The user, service, or device represented by a request. | 请求背后代表的用户、服务或设备。 |
| Credential | 凭证 | Information used to prove or support an identity claim. | 用来证明身份或支持身份声明的信息。 |
| Password | 密码 | A secret value used to help prove a user’s identity. | 帮助证明用户身份的一串秘密字符。 |
| Session | 会话 | Server-side state that remembers a verified identity across requests. | 服务器记住已验证身份的一段状态。 |
| Token | 令牌 | A protected value that represents a verified identity or granted access. | 代表已验证身份或已授予访问权的一段受保护信息。 |
| Authorization | 授权 | Checking what an identity is allowed to do. | 检查这个身份可以执行哪些操作。 |
09 · What to Remember
Authentication answers “Who are you?” by verifying a user, service, or device.
It creates a trusted identity that later authorization checks can use.