認証と認可
異なるMicro Frontend間で堅牢な認証・認可の仕組みを実装します。
「認証と認可」はCoddyKit上の無料Micro Frontends Architecture with Module Federationレッスンです。 これはレッスン1/4です。 下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。 これはMicro Frontends Architecture with Module Federation学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Micro Frontends Architecture with Module Federationコースには全4レッスンが含まれています。
このレッスンの一部はまだ翻訳されておらず、英語で表示されています。
Auth & Auth in MFEs
Welcome to Authentication & Authorization in Micro Frontends! Securing federated applications brings unique challenges compared to monolithic apps.
We need robust ways to verify user identities (authentication) and control what they can access (authorization) across independently developed and deployed Micro Frontends.
Centralized Authentication Need
In a Micro Frontend architecture, users interact with multiple separate applications. If each MFE handled authentication independently, users would face multiple login prompts.
This leads to a poor user experience and complex session management. A centralized authentication mechanism is crucial for seamless navigation.
Identity Providers (IdP)
A common solution is to use an Identity Provider (IdP). This is a service that creates, maintains, and manages identity information for users and authenticates them.
- Examples: Auth0, Okta, Keycloak, or a custom OAuth 2.0/OpenID Connect server.
- The IdP handles the login process and issues security tokens (like JWTs) upon successful authentication.
Authentication Flow Overview
Here's a simplified centralized authentication flow:
- User tries to access any MFE.
- If not authenticated, they are redirected to the central IdP login page.
- User logs in with the IdP.
- IdP redirects the user back to the MFE with a security token.
- The MFE stores this token (e.g., in an HTTP-only cookie or local storage).
All subsequent requests from any MFE will use this token.
Sharing Authentication State
Once a user is authenticated, their session or token needs to be available to all Micro Frontends. Common strategies for sharing state:
- HTTP-Only Cookies: Secure and automatically sent with requests.
- Web Storage (localStorage/sessionStorage): Accessible across same-origin domains.
- Shared Libraries/Context: A shared utility that wraps token management, often exposed via Module Federation.
Each method has its trade-offs regarding security and ease of implementation.
Authorization Explained
While authentication verifies who you are, authorization determines what you can do.
- After authentication, the security token often contains user roles or permissions.
- Each Micro Frontend is then responsible for checking these permissions before granting access to specific features or data.
Role-Based Access Control (RBAC)
Role-Based Access Control (RBAC) is a popular authorization strategy. Users are assigned roles (e.g., 'admin', 'editor', 'viewer'), and each role has specific permissions.
Micro Frontends simply check the user's roles against the required roles for a given action or component.
Implementing Auth Checks
Each Micro Frontend or its backend API can implement authorization checks. This often involves:
- Decoding the security token to extract user roles/permissions.
- Comparing these against the required permissions for a specific action or UI element.
Here's a simple JavaScript example:
function hasPermission(userRoles, requiredRole) {
if (!userRoles || !requiredRole) return false;
return userRoles.includes(requiredRole);
}
// Imagine user roles are parsed from a JWT
const currentUserRoles = ["user", "editor"];
// Check if user can 'edit_post'
const canEdit = hasPermission(currentUserRoles, "editor");
// Check if user can 'delete_user'
const canDelete = hasPermission(currentUserRoles, "admin");
console.log("Can edit post?", canEdit);
console.log("Can delete user?", canDelete);Security Best Practices
Securing your federated applications requires vigilance:
- HTTPS: Always use HTTPS for all communication.
- Token Storage: Store sensitive tokens securely (e.g., HTTP-only cookies over localStorage).
- CORS: Properly configure Cross-Origin Resource Sharing policies.
- Input Validation: Always validate user input on both client and server sides.
- Regular Audits: Perform security audits and keep dependencies updated.
Order the Auth Flow
Drag and drop the steps to correctly order a user's initial authentication flow in a federated application using an Identity Provider (IdP).
Recap: Secure MFEs
We've covered the essentials of authentication and authorization in Micro Frontends. Key takeaways:
- Centralized authentication via an Identity Provider ensures a smooth user experience.
- Security tokens (like JWTs) carry authentication and authorization data.
- Strategies like HTTP-only cookies or shared libraries help share authentication state.
- Authorization (e.g., RBAC) dictates what users can do, based on roles/permissions in their token.
- Always follow security best practices like HTTPS and secure token storage.
Next, we'll explore cross-application security risks!
よくある質問
「認証と認可」レッスンは無料ですか？
はい。「認証と認可」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Micro Frontends Architecture with Module Federationコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Micro Frontends Architecture with Module Federationコースには全4レッスンが含まれています。
「認証と認可」で何を学びますか？
異なるMicro Frontend間で堅牢な認証・認可の仕組みを実装します。 ブラウザで直接実行するハンズオンコードでMicro Frontends Architecture with Module Federationを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。
Micro Frontends Architecture with Module Federationを始めるのに経験は必要ですか？
事前経験は必要ありません。CoddyKitのMicro Frontends Architecture with Module Federationは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。 これはレッスン1/4です。
「認証と認可」レッスンにはどのくらい時間がかかりますか？
ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。
このMicro Frontends Architecture with Module Federationレッスンでコードを書いて実行できますか？
はい。すべてのMicro Frontends Architecture with Module Federationレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。