使用自定义用户对象时Spring Session Redis集成问题咨询

Hey there! Let's walk through how to handle custom user objects with Spring Session backed by Redis—since you've already got the dependencies and basic config set up, here's what you need to focus on:

First off, your custom user object needs to be serializable so Redis can store it. You have two common options here:

• JDK Serialization: Implement the Serializable interface directly (simple but less flexible for complex objects):

  public class CustomUser implements Serializable {
      private Long userId;
      private String username;
      private String fullName;
      // Getters, setters, and constructors
  }
  

• Jackson JSON Serialization (recommended): Avoids JDK serialization's limitations like poor performance and tight class coupling. We'll configure this next.

By default, Spring Session uses JDK serialization for Redis storage. To switch to Jackson (which stores objects as readable JSON), update your SessionConfig class:

@Configuration
@EnableRedisHttpSession
public class SessionConfig {

    // Override the default serializer to use Jackson
    @Bean
    public RedisSerializer<Object> springSessionDefaultRedisSerializer() {
        return new GenericJackson2JsonRedisSerializer();
    }
}

This ensures your custom user object gets serialized to JSON when stored in Redis, making it easier to debug and compatible with future class changes.

Once your class and config are set, you can interact with the session like you would with any object:

@Controller
public class UserSessionController {

    // Store custom user in session after login
    @PostMapping("/login")
    public String handleLogin(HttpSession session, @RequestParam String username) {
        CustomUser loggedInUser = fetchUserFromDatabase(username); // Your user lookup logic
        session.setAttribute("loggedInUser", loggedInUser);
        return "redirect:/dashboard";
    }

    // Retrieve custom user from session
    @GetMapping("/dashboard")
    public String showDashboard(HttpSession session, Model model) {
        // Safely retrieve the user (use Optional to avoid null pointer exceptions)
        CustomUser loggedInUser = Optional.ofNullable(
                (CustomUser) session.getAttribute("loggedInUser")
        ).orElseThrow(() -> new UnauthorizedException("User not logged in"));
        
        model.addAttribute("user", loggedInUser);
        return "dashboard";
    }
}

• If your custom user has nested objects, ensure those nested classes are also compatible with your serialization method (either implement Serializable or ensure Jackson can serialize them).
• Add @JsonIgnoreProperties(ignoreUnknown = true) to your CustomUser class if you plan to modify the class structure later (e.g., add new fields)—this prevents deserialization failures when reading old session data.

  @JsonIgnoreProperties(ignoreUnknown = true)
  public class CustomUser implements Serializable {
      // ... class fields and methods
  }
  

You can check if your user object is stored correctly using the Redis CLI:

# List all Spring Session keys
redis-cli KEYS "spring:session:*"

# Fetch the full session data using the session ID key
redis-cli HGETALL "spring:session:sessions:your-session-id-here"

Look for the sessionAttr:loggedInUser entry—you should see the JSON representation of your custom user.

内容的提问来源于stack exchange，提问作者AKrush95