Encoded password does not look like BCrypt

Is it just me or has anyone else got an error like o.s.s.c.bcrypt.BCryptPasswordEncoder : Encoded password does not look like BCrypt?

public class WebSecurityConfig extends WebSecurityConfigurerAdapter {
   @Autowired
    CustomUserDetailsService customUserDetailsService;
   .....
   @Bean
    public static PasswordEncoder passwordEncoder() {
        return new BCryptPasswordEncoder(16);
    }
    @Override
    protected void configure(AuthenticationManagerBuilder auth) throws Exception {
        auth.authenticationProvider(authenticationProvider());
    }
    @Bean
    public DaoAuthenticationProvider authenticationProvider() {
        DaoAuthenticationProvider authenticationProvider = new DaoAuthenticationProvider();
        authenticationProvider.setUserDetailsService(customUserDetailsService);
        authenticationProvider.setPasswordEncoder(passwordEncoder());
        return authenticationProvider;
    }
}

Service:

@Autowired
    PasswordEncoder passwordEncoder;
user.setPassword(passwordEncoder.encode(user.getPassword()));

The encrypted password looks like $2a$16$AYSTH/JEPXPwqYBRswLq0emwmItvsQgf.dnaffXGJpvYML97bBoGe in the db, but when I try to log in, I get the error. P.s.: I am using this with OAuth2 Spring boot 5.0.4.RELEASE

[AlicanBalik]

Sure. First, open your security configuration which extends WebSecurityConfigurerAdapter and paste below function:

@Bean
public static PasswordEncoder passwordEncoder() {
      return PasswordEncoderFactories.createDelegatingPasswordEncoder();
}

Then in the same configuration file, modify your authenticationProvider() function like this:

 @Bean
 public DaoAuthenticationProvider authenticationProvider() {
      DaoAuthenticationProvider authenticationProvider = new DaoAuthenticationProvider();
      authenticationProvider.setUserDetailsService(customUserDetailsService);
      authenticationProvider.setPasswordEncoder(passwordEncoder());
      return authenticationProvider;
 }

Note: If you create multiple PasswordEncoder beans, the compiler will always select the first one. If you also need to implement NoOpPasswordEncoder, do it in the file that you really need to use it and create it without @Bean.

@SuppressWarnings("deprecation")
 public static NoOpPasswordEncoder passwordEncoder() {
     return (NoOpPasswordEncoder) NoOpPasswordEncoder.getInstance();
 }

In your service, or wherever you want to use you need to autowire the `PasswordEncoder`:

@Autowired
private PasswordEncoder passwordEncoder;

And you can encrypt your String like this: `passwordEncoder.encode("password");`
If you want to match a raw password with an encrypted one, you can do it with `passwordEncoder.matches("rawPassword", user.getPassword());` where `user.getPassword()` returns an encrypted password (from db).

[AlicanBalik]

Yes, I did. If you also have the same problem, you can follow here