Spring项目启动失败：PasswordEncoder Bean未被识别的解决方案咨询

Hey, let’s figure out why your PasswordEncoder bean isn’t being detected even though you’ve defined it in your SecuritySettings class. Here are the most common fixes to try:

1. Verify Component Scanning Coverage #

Spring needs to scan your SecuritySettings class to register the PasswordEncoder bean. Make sure:

• The SecuritySettings class is in the same package (or a sub-package) as your main Spring Boot application class. For example, if your main app is com.example.socialplatform.Application, SecuritySettings should be in com.example.socialplatform or com.example.socialplatform.config.
• If it’s in a different package, add @ComponentScan to your main application class to explicitly include that package:

  @SpringBootApplication
  @ComponentScan(basePackages = {"com.example.socialplatform", "com.your.other.package"})
  public class Application {
      public static void main(String[] args) {
          SpringApplication.run(Application.class, args);
      }
  }
  

2. Ensure AuthorizationService is Managed by Spring #

Your error mentions the AuthorizationService constructor can’t find the PasswordEncoder bean. Double-check that AuthorizationService is annotated with @Service (or @Component) so Spring creates it as a managed bean:

@Service
public class AuthorizationService {
    private final PasswordEncoder passwordEncoder;

    // Constructor injection (Spring will auto-wire the PasswordEncoder if both beans are registered)
    public AuthorizationService(PasswordEncoder passwordEncoder) {
        this.passwordEncoder = passwordEncoder;
    }

    // Your service methods here...
}

Without @Service, Spring won’t recognize this class as a bean, so it can’t resolve the constructor dependency.

3. Confirm the @Bean Method is Accessible #

While your code shows a public encoder() method, it’s worth double-checking you didn’t accidentally set it to private or protected. Spring requires @Bean methods to be public to register them correctly.

4. Validate Spring Security Dependencies #

Make sure your pom.xml (for Maven) includes the correct Spring Security starter dependency—missing or incorrect versions can cause bean registration issues:

<dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-security</artifactId>
</dependency>

5. Clear Caches and Rebuild #

You mentioned trying Maven commands, but sometimes IDE caches can interfere. Try:

• Running mvn clean install from the terminal to do a full clean build.
• In IntelliJ IDEA, go to File > Invalidate Caches... and restart the IDE.
• In Eclipse, go to Project > Clean and rebuild your project.

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