تنفيذ UserDetailsService مخصّص
أنشئ `UserDetailsService` مخصّصًا لتحميل بيانات خاصة بالمستخدم من مخزن بيانات تطبيقك بغرض المصادقة.
تنفيذ UserDetailsService مخصّص درس مجاني في Spring Security 6 & JWT Authentication على CoddyKit. هذا هو الدرس 1 من أصل 4. يمكنك قراءة الدرس كاملاً أدناه مجاناً — ثم تمرن عليه مباشرة في المتصفح باستخدام محرر أكواد مدمج ومدرس ذكاء اصطناعي متاح 24/7. هذا الدرس جزء من مسار التعلم في Spring Security 6 & JWT Authentication، وتقدمك يتزامن عبر الويب وتطبيق CoddyKit. تتضمن دورة Spring Security 6 & JWT Authentication 4 دروس في المجموع.
بعض أجزاء هذا الدرس لم تُترجم بعد وتظهر باللغة الإنجليزية.
Beyond In-Memory Users
In previous lessons, you might have used in-memory users for simple authentication. This means usernames and passwords are hardcoded directly in your application's configuration.
While easy for testing, real-world applications need to load user data from a persistent source like a database, LDAP, or another service. This is where a custom UserDetailsService comes in!
The UserDetailsService Interface
Spring Security uses the UserDetailsService interface to retrieve user-specific data during authentication. It has just one method you need to implement:
UserDetails loadUserByUsername(String username)
This method is crucial. When a user tries to log in, Spring Security calls this method, passing the username provided by the user.
What is UserDetails?
The loadUserByUsername method must return a UserDetails object. This interface represents the authenticated user's information, including:
- Username
- Password
- Authorities (roles/permissions)
- Account status (e.g., enabled, locked, expired)
Spring Security provides a default implementation called org.springframework.security.core.userdetails.User that you'll often use.
Creating Your Custom Service
To create a custom user service, you simply create a class that implements UserDetailsService. Inside, you'll override the loadUserByUsername method.
This method is where you'll write the logic to fetch user data from your chosen data store. For now, we'll use some hardcoded examples.
Implementing loadUserByUsername
Inside loadUserByUsername, you'll perform these steps:
- Receive the
username. - Look up the user in your data source.
- If found, create a
UserDetailsobject with their details (username, password, roles). - If not found, throw a
UsernameNotFoundException.
Remember, password encoding is vital for security, but we'll cover that in a later lesson. For now, we'll use a plain text password prefix: {noop}.
Code: Basic UserDetailsService
Let's see a simple implementation. This example hardcodes users, simulating fetching from a data source. Run it to see how it works!
import org.springframework.security.core.userdetails.User;
import org.springframework.security.core.userdetails.UserDetails;
import org.springframework.security.core.userdetails.UserDetailsService;
import org.springframework.security.core.userdetails.UsernameNotFoundException;
import java.util.Arrays;
import java.util.Collections;
class MyUserDetailsService implements UserDetailsService {
@Override
public UserDetails loadUserByUsername(String username) throws UsernameNotFoundException {
// In a real app, you'd fetch user from a database
if ("user".equals(username)) {
return User.withUsername("user")
.password("{noop}password") // {noop} for plain text
.roles("USER")
.build();
}
if ("admin".equals(username)) {
return User.withUsername("admin")
.password("{noop}adminpass")
.roles("ADMIN", "USER")
.build();
}
throw new UsernameNotFoundException("User not found: " + username);
}
}
public class Main {
public static void main(String[] args) {
MyUserDetailsService service = new MyUserDetailsService();
System.out.println("Attempting to load 'user'...");
try {
UserDetails user = service.loadUserByUsername("user");
System.out.println("Loaded User: " + user.getUsername());
System.out.println("Authorities: " + user.getAuthorities());
} catch (UsernameNotFoundException e) {
System.out.println(e.getMessage());
}
System.out.println("\nAttempting to load 'admin'...");
try {
UserDetails admin = service.loadUserByUsername("admin");
System.out.println("Loaded Admin: " + admin.getUsername());
System.out.println("Authorities: " + admin.getAuthorities());
} catch (UsernameNotFoundException e) {
System.out.println(e.getMessage());
}
System.out.println("\nAttempting to load 'unknown'...");
try {
service.loadUserByUsername("unknown");
} catch (UsernameNotFoundException e) {
System.out.println(e.getMessage());
}
}
}Adding Roles and Authorities
Notice in the example, we used .roles("USER") and .roles("ADMIN", "USER").
- Roles are high-level permissions, like 'ADMIN' or 'USER'.
- These roles are converted into GrantedAuthority objects by Spring Security.
- When building the
UserDetailsobject, you specify the roles/authorities the user possesses.
These authorities are later used by Spring Security for authorization (determining what a user can access).
Registering Your Service
Once you've created your custom UserDetailsService, Spring Security needs to know about it. In a Spring Boot application, you typically register it as a Spring bean.
By simply defining your custom service as a @Bean, Spring Security's auto-configuration will usually pick it up and use it for authentication.
The Custom Authentication Flow
Here's how custom authentication typically works with your service:
- User submits login credentials (username, password).
- Spring Security receives the request.
- It calls your custom
UserDetailsService'sloadUserByUsername()method with the provided username. - Your method fetches user data and returns a
UserDetailsobject. - Spring Security then compares the provided password with the password from
UserDetails(after encoding/decoding). - If they match, authentication succeeds!
Check Your Understanding
Consider the core purpose and components of implementing a custom UserDetailsService.
Recap: Custom UserDetailsService
You've learned how to implement a custom UserDetailsService, a fundamental component for advanced user authentication in Spring Security:
- It allows loading user data from any source.
- You implement the
loadUserByUsernamemethod. - This method returns a
UserDetailsobject, containing user credentials and authorities. - It's essential for moving beyond in-memory user management.
Next, we'll dive into securing those passwords with proper encoding!
الأسئلة الشائعة
هل درس «تنفيذ UserDetailsService مخصّص» مجاني؟
نعم — نص درس «تنفيذ UserDetailsService مخصّص» كامل متاح مجاناً هنا على الويب. لتمرينه بشكل تفاعلي (محرر أكواد مدمج ومدرس ذكاء اصطناعي متاح 24/7) وفتح باقي دورة Spring Security 6 & JWT Authentication، انتقل إلى CoddyKit PRO. تتضمن دورة Spring Security 6 & JWT Authentication 4 دروس في المجموع.
ماذا ستتعلم في «تنفيذ UserDetailsService مخصّص»؟
أنشئ `UserDetailsService` مخصّصًا لتحميل بيانات خاصة بالمستخدم من مخزن بيانات تطبيقك بغرض المصادقة. تتمرن على Spring Security 6 & JWT Authentication مع أكواد عملية تشغلها مباشرة في المتصفح، ومدرس ذكاء اصطناعي متاح 24/7 يجيب على أسئلتك أثناء عملك.
هل أحتاج إلى خبرة سابقة لأبدأ Spring Security 6 & JWT Authentication؟
لا تُشترط خبرة سابقة. Spring Security 6 & JWT Authentication على CoddyKit منظم للمبتدئين حتى المتقدمين، لذا يمكنك البدء من هنا أو من البداية والتقدم بسرعتك الخاصة. هذا هو الدرس 1 من أصل 4.
كم من الوقت يستغرق درس «تنفيذ UserDetailsService مخصّص»؟
معظم دروس CoddyKit تستغرق حوالي 5–10 دقائق. كل منها موجز وتفاعلي، لذا تحرز تقدماً مستمراً وتستأنف من حيث توقفت عبر الويب والتطبيق.
هل يمكنني كتابة وتشغيل أكواد في درس Spring Security 6 & JWT Authentication هذا؟
نعم. كل درس في Spring Security 6 & JWT Authentication يتضمن محرر أكواد مدمج، لذا تكتب وتشغل أكواداً حقيقية مباشرة في متصفحك وتحصل على تعليقات فورية من الذكاء الاصطناعي — بدون إعداد محلي.
جميع الدروس في هذه الدورة
- تنفيذ UserDetailsService مخصّص
- فهم مشفّرات كلمات المرور
- دمج إدارة المستخدمين في قاعدة البيانات
- التفويض القائم على الأدوار باستخدام السلطات الممنوحة