身份验证与授权
实现用户身份验证和授权策略，保护边缘 API 端点的安全
身份验证与授权 是 CoddyKit 上的免费 Edge Computing with Cloudflare Workers & Deno 课时。 这是第 1 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Edge Computing with Cloudflare Workers & Deno 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Edge Computing with Cloudflare Workers & Deno 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Securing Edge APIs
Welcome! In this lesson, we'll dive into Authentication and Authorization for your edge API endpoints.
These are crucial concepts for protecting your applications and ensuring only the right users can access specific resources.
AuthN vs. AuthZ
Let's clarify two key terms:
- Authentication (AuthN): Verifies who you are. Think of it like showing your ID to prove your identity.
- Authorization (AuthZ): Determines what you can do. This is like your ID granting you access to certain areas, but not others.
They often work together, but are distinct processes.
Common Edge Auth Methods
At the edge, we need lightweight and efficient authentication methods. Common approaches include:
- API Keys: Simple secrets used to identify an application or user.
- JSON Web Tokens (JWTs): Self-contained, digitally signed tokens for secure information exchange.
- OAuth/OIDC: More complex protocols for delegated authorization, often relying on JWTs.
We'll focus on API Keys and JWTs.
Implementing API Key Auth
API Keys are straightforward. A client sends a secret key, usually in a header, and your Worker validates it. Let's see a simple example:
export default {
async fetch(request, env, ctx) {
const apiKey = request.headers.get('X-API-Key');
// In a real app, fetch 'MY_API_KEY' from env.MY_API_KEY
if (apiKey !== 'super-secret-key-123') {
return new Response('Unauthorized: Invalid API Key', { status: 401 });
}
return new Response('Access Granted!', { status: 200 });
},
};API Key Auth Explained
In the example, the Worker checks for the X-API-Key header. If it doesn't match our expected secret, access is denied with a 401 Unauthorized status.
For production, always store your API keys securely, typically in Cloudflare Worker environment variables, not directly in your code.
JSON Web Tokens (JWTs)
JWTs are powerful for edge applications because they are self-contained. Once issued by an identity provider, a JWT can be verified by your Worker without needing to contact a central server every time.
A JWT has three parts: Header, Payload, and Signature, separated by dots.
Verifying JWTs on the Edge
Your Worker will receive a JWT, usually in the Authorization: Bearer header. The critical step is to verify its signature to ensure it hasn't been tampered with.
While full cryptographic verification requires a library, here's where you'd typically extract and prepare for verification:
export default {
async fetch(request, env, ctx) {
const authHeader = request.headers.get('Authorization');
if (!authHeader || !authHeader.startsWith('Bearer ')) {
return new Response('Unauthorized: No token', { status: 401 });
}
const token = authHeader.split(' ')[1];
// In a real app, you'd use a crypto library and a secret key
// to verify the token's signature, expiry, and claims.
// e.g., using 'jose' library with `await jwtVerify(token, secretKey)`
if (token) {
// For this example, we'll assume a successful (mock) verification
return new Response('Access Granted with JWT!', { status: 200 });
}
return new Response('Unauthorized: Invalid JWT', { status: 401 });
},
};Role-Based Authorization (RBAC)
Once a user is authenticated (e.g., via a verified JWT), you need to decide what actions they are authorized to perform. This is where Role-Based Access Control (RBAC) comes in.
RBAC assigns permissions to roles (e.g., 'admin', 'user', 'guest'), and users are assigned one or more roles. Your Worker then checks the user's role before allowing an action.
Implementing RBAC in Worker
You can embed user roles or permissions directly into the JWT payload as 'claims'. After verifying the JWT, your Worker can read these claims and enforce authorization rules.
export default {
async fetch(request, env, ctx) {
// Assume JWT is already verified and we have the user's role
// In a real app, this 'userRole' would come from the decoded JWT payload.
const userRole = 'editor'; // Example role from a verified token
if (request.url.includes('/admin') && userRole !== 'admin') {
return new Response('Forbidden: Admins only!', { status: 403 });
}
if (request.method === 'POST' && userRole === 'guest') {
return new Response('Forbidden: Guests cannot create!', { status: 403 });
}
return new Response(`Welcome, ${userRole}! Request processed.`, { status: 200 });
},
};Test Your Understanding
Which of the following statements correctly describe the difference between Authentication and Authorization?
Recap: AuthN & AuthZ
Great job! You've learned the fundamentals of securing your edge APIs.
- Authentication confirms identity.
- Authorization controls access.
- API Keys offer simple authentication.
- JWTs provide secure, self-contained authentication and can carry authorization claims.
- RBAC (Role-Based Access Control) helps define permissions based on user roles.
These strategies are vital for building robust and secure edge applications.
常见问题解答
「身份验证与授权」课时是免费的吗？
是的 — 「身份验证与授权」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Edge Computing with Cloudflare Workers & Deno 课程的其余内容，请升级到 CoddyKit PRO。 Edge Computing with Cloudflare Workers & Deno 课程共包含 4 节课。
「身份验证与授权」这节课中我会学到什么？
实现用户身份验证和授权策略，保护边缘 API 端点的安全 你通过在浏览器中直接运行的动手代码来练习 Edge Computing with Cloudflare Workers & Deno，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Edge Computing with Cloudflare Workers & Deno 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Edge Computing with Cloudflare Workers & Deno 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 1 节课，共 4 节。
「身份验证与授权」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Edge Computing with Cloudflare Workers & Deno 课中编写并运行代码吗？
能。每节 Edge Computing with Cloudflare Workers & Deno 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。