Spring Security 6 & JWT Authentication · 课时

生产环境安全加固

应用必要的安全配置和实践，为生产环境加固您的 Spring Security 应用。

第 1 / 4 课11 个步骤

生产环境安全加固 是 CoddyKit 上的免费 Spring Security 6 & JWT Authentication 课时。这是第 1 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Spring Security 6 & JWT Authentication 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Spring Security 6 & JWT Authentication 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Production Hardening Intro

Welcome to Production Security Hardening! Securing an application in development is one thing, but production environments demand much higher vigilance.

In this lesson, we'll explore essential configurations and best practices to protect your Spring Security application when it goes live.

This isn't just about fixing bugs; it's about building a robust defense against real-world threats.

Why HTTPS is Non-Negotiable

In production, all communication between clients and your server must be encrypted using HTTPS (HTTP Secure).

Data Confidentiality: Protects sensitive data (passwords, personal info) from eavesdropping.
Data Integrity: Ensures data isn't tampered with during transmission.
Authentication: Verifies the server's identity to the client.

Without HTTPS, your application is vulnerable to Man-in-the-Middle (MITM) attacks.

Enforcing HTTPS with Spring Security

Spring Security can enforce that all requests must use a secure channel (HTTPS). If an HTTP request comes in, it will be redirected to HTTPS (if your server is configured for SSL).

The requiresSecure() method ensures this. Try running this minimal Spring Boot app and observe its behavior if you try to access it via HTTP (e.g., http://localhost:8080).

import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.security.config.annotation.web.builders.HttpSecurity;
import org.springframework.security.config.annotation.web.configuration.EnableWebSecurity;
import org.springframework.security.web.SecurityFilterChain;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
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.provisioning.InMemoryUserDetailsManager;

@SpringBootApplication
public class HardeningApp {
    public static void main(String[] args) {
        SpringApplication.run(HardeningApp.class, args);
    }

    @Configuration
    @EnableWebSecurity
    static class SecurityConfig {

        @Bean
        public SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception {
            http
                .authorizeHttpRequests(authorize -> authorize
                    .anyRequest().authenticated()
                )
                .requiresChannel(channel -> channel
                    .anyRequest().requiresSecure() // Enforce HTTPS
                )
                .formLogin(); // Basic form login for testing
            return http.build();
        }

        @Bean
        public UserDetailsService userDetailsService() {
            UserDetails user = User.withDefaultPasswordEncoder()
                .username("user")
                .password("password")
                .roles("USER")
                .build();
            return new InMemoryUserDetailsManager(user);
        }
    }
}

Overview of Security Headers

HTTP Security Headers are crucial for preventing common web vulnerabilities. They instruct browsers on how to behave when interacting with your application.

Key headers to configure:

HSTS (Strict-Transport-Security): Forces browsers to use HTTPS for future visits.
CSP (Content-Security-Policy): Prevents XSS attacks by restricting content sources.
X-Frame-Options: Stops clickjacking by controlling if your site can be embedded in an iframe.
X-Content-Type-Options: Prevents MIME-sniffing attacks.
Referrer-Policy: Controls how much referrer information is sent.

Configuring Security Headers

Spring Security provides convenient methods to configure these headers via HttpSecurity.headers(). This ensures your application's responses always include these vital instructions for the client's browser.

Here's how you can set up some common security headers in your configuration:

import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.security.config.annotation.web.builders.HttpSecurity;
import org.springframework.security.config.annotation.web.configuration.EnableWebSecurity;
import org.springframework.security.web.SecurityFilterChain;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
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.provisioning.InMemoryUserDetailsManager;
import org.springframework.security.web.header.writers.ReferrerPolicyHeaderWriter;

@SpringBootApplication
public class HeaderApp {
    public static void main(String[] args) {
        SpringApplication.run(HeaderApp.class, args);
    }

    @Configuration
    @EnableWebSecurity
    static class SecurityConfig {

        @Bean
        public SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception {
            http
                .authorizeHttpRequests(authorize -> authorize
                    .anyRequest().authenticated()
                )
                .headers(headers -> headers
                    .httpStrictTransportSecurity(hsts -> hsts
                        .includeSubDomains(true)
                        .maxAgeInSeconds(31536000) // 1 year
                    )
                    .contentSecurityPolicy(csp -> csp
                        .policyDirectives("default-src 'self'; script-src 'self' 'unsafe-inline'; object-src 'none'")
                    )
                    .frameOptions(frameOptions -> frameOptions.deny()) // X-Frame-Options: DENY
                    .xContentTypeOptions() // X-Content-Type-Options: nosniff
                    .referrerPolicy(referrer -> referrer
                        .policy(ReferrerPolicyHeaderWriter.ReferrerPolicy.NO_REFERRER)
                    )
                )
                .formLogin();
            return http.build();
        }

        @Bean
        public UserDetailsService userDetailsService() {
            UserDetails user = User.withDefaultPasswordEncoder()
                .username("user")
                .password("password")
                .roles("USER")
                .build();
            return new InMemoryUserDetailsManager(user);
        }
    }
}

Disabling Sensitive Endpoints

In production, you should disable or restrict access to any endpoints that could reveal sensitive information or allow unintended control.

Actuator Endpoints: Spring Boot Actuator provides useful operational insights (/actuator/**). In production, expose only necessary endpoints (e.g., /health, /info) and secure them.
HTTP TRACE/OPTIONS Methods: These methods can sometimes be exploited for information disclosure or cross-site tracing attacks. It's often best to disable them.

Always review what's exposed and ensure it's absolutely necessary and secured.

Custom Error Handling

Default error pages in development can expose stack traces and internal server details, which are valuable to attackers.

In production, configure custom error pages that provide minimal information. For example, a simple 'Error 500 - Internal Server Error' message without specifics.

Spring Boot allows you to define custom error pages (e.g., src/main/resources/public/error.html or src/main/resources/templates/error/404.html for specific status codes).

Secure Session Management

Session cookies are critical for maintaining user state, so they need robust protection. Spring Security helps, but you can further harden them.

HttpOnly: Prevents client-side scripts from accessing the cookie.
Secure: Ensures the cookie is only sent over HTTPS.
SameSite: Mitigates CSRF attacks by restricting when cookies are sent with cross-site requests (Lax or Strict).

These are often configured in application.properties, but Spring Security's sessionManagement() also offers controls.

import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.security.config.annotation.web.builders.HttpSecurity;
import org.springframework.security.config.annotation.web.configuration.EnableWebSecurity;
import org.springframework.security.web.SecurityFilterChain;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.security.config.http.SessionCreationPolicy;
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.provisioning.InMemoryUserDetailsManager;

@SpringBootApplication
public class SessionApp {
    public static void main(String[] args) {
        SpringApplication.run(SessionApp.class, args);
    }

    @Configuration
    @EnableWebSecurity
    static class SecurityConfig {

        @Bean
        public SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception {
            http
                .authorizeHttpRequests(authorize -> authorize
                    .anyRequest().authenticated()
                )
                .sessionManagement(session -> session
                    .sessionCreationPolicy(SessionCreationPolicy.IF_REQUIRED) // Default, but good to be explicit
                    .sessionFixation().migrateSession() // Protects against session fixation attacks
                )
                .csrf(csrf -> csrf.disable()) // CSRF is enabled by default, disable for simplicity in this example
                .formLogin();
            return http.build();
        }

        @Bean
        public UserDetailsService userDetailsService() {
            UserDetails user = User.withDefaultPasswordEncoder()
                .username("user")
                .password("password")
                .roles("USER")
                .build();
            return new InMemoryUserDetailsManager(user);
        }
    }
}

Secure Secrets Management

Never hardcode sensitive information (secrets) like database credentials, API keys, or encryption keys directly in your code or configuration files.

Best practices for managing secrets in production:

Environment Variables: Load secrets from environment variables.
Externalized Configuration: Use Spring Cloud Config Server or similar tools.
Dedicated Secret Management Services: HashiCorp Vault, AWS Secrets Manager, Azure Key Vault are designed for this purpose.

This prevents secrets from being exposed in source control or build artifacts.

Production Hardening Check

Which of the following are recommended practices for hardening a Spring Security application in a production environment? Select all that apply.

在交互式课程中回答

Recap & Next Steps

Great job! You've learned crucial steps to harden your Spring Security application for production.

We covered:

The necessity of HTTPS and how to enforce it.
Configuring vital HTTP security headers.
Restricting sensitive endpoints and providing custom error pages.
Implementing secure session management practices.
Best practices for managing secrets.

These practices form a strong foundation for a secure deployment. Next, we'll dive into logging and monitoring security events to detect and respond to threats effectively.

免费开始

用 AI 导师学习 Java — 免费

在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。

课程: 12
课程: 48

免费开始学习查看完整课程

常见问题解答

「生产环境安全加固」课时是免费的吗？

是的 — 「生产环境安全加固」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Spring Security 6 & JWT Authentication 课程的其余内容，请升级到 CoddyKit PRO。 Spring Security 6 & JWT Authentication 课程共包含 4 节课。

「生产环境安全加固」这节课中我会学到什么？

应用必要的安全配置和实践，为生产环境加固您的 Spring Security 应用。你通过在浏览器中直接运行的动手代码来练习 Spring Security 6 & JWT Authentication，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Spring Security 6 & JWT Authentication 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Spring Security 6 & JWT Authentication 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 1 节课，共 4 节。

「生产环境安全加固」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Spring Security 6 & JWT Authentication 课中编写并运行代码吗？

能。每节 Spring Security 6 & JWT Authentication 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Spring Security 6 & JWT Authentication