Kimlik Doğrulama ve Yetkilendirme

In system design, authentication and authorization are critical for security. They control who can access your system and what they can do.

• Authentication (AuthN) verifies who you are.
• Authorization (AuthZ) determines what you're allowed to do.

Think of it like a club: authentication is checking your ID at the door, authorization is seeing if you have a VIP pass to enter special areas.

Authentication is the process of proving your identity to a system. This confirms that you are who you claim to be.

Common authentication methods include:

• Password-based: Username and password.
• Multi-factor: Combining passwords with codes from an app or SMS.
• Biometric: Fingerprints or facial recognition.
• Token-based: Using a cryptographic token after initial login.

Token-based authentication is popular for web and mobile apps. After a user logs in (authenticates) with credentials, the server issues a token.

This token is then sent with every subsequent request to prove the user's identity without sending credentials repeatedly. A common type is the JSON Web Token (JWT).

A JWT (JSON Web Token) is a compact, URL-safe means of representing claims to be transferred between two parties. It's often used to authenticate users.

JWTs consist of three parts, separated by dots:

1. Header: Type of token and signing algorithm.
2. Payload: Claims (user ID, roles, expiration).
3. Signature: Used to verify the token hasn't been tampered with.

It looks something like this:

When a client sends a request with a token, the server must validate it. This often involves checking the signature and expiration.

Here's a very simplified conceptual example of how a server might check if a token is known, representing a basic validation step:

Authorization is the process of determining what an authenticated user or system is permitted to do.

For example, a regular user might be able to view their own profile, but only an administrator can delete user accounts. Authorization answers the question: "Are you allowed to do that?"

One common authorization model is Role-Based Access Control (RBAC). In RBAC, permissions are associated with roles, and users are assigned to roles.

• Users: Individuals or systems.
• Roles: Collections of permissions (e.g., 'Admin', 'Editor', 'Viewer').
• Permissions: Specific actions on resources (e.g., 'read_post', 'edit_user').

This simplifies managing access, as you assign users to roles rather than individual permissions.

For more complex scenarios, Policy-Based Authorization (like Attribute-Based Access Control or ABAC) allows for very fine-grained control.

Instead of just roles, access decisions are based on attributes of the user, the resource, the environment, and the action itself. This offers greater flexibility but can be more complex to manage.

Authentication and authorization work hand-in-hand in a typical request flow:

1. A user tries to access a resource.
2. The system authenticates the user (e.g., validates their token). If invalid, access is denied.
3. If authenticated, the system then authorizes the user: it checks if the user's role or attributes grant them permission for that specific action on that resource.
4. If authorized, access is granted. Otherwise, it's denied.

Which of the following statements correctly describe the concepts of Authentication and Authorization?

We've explored the crucial difference between authentication (who you are) and authorization (what you can do).

You learned about token-based authentication with JWTs and authorization models like RBAC. Understanding these concepts is fundamental to designing secure and robust systems.

Keep practicing these distinctions as you design systems that need to control access effectively!