BroadleafCommerce/BroadleafCommerce

@chiranjitsaha1108 Spring security provides an AES encryption approach using bcrypt. That encryption algorithm can be enabled in the product using the following setting (in perhaps common-shared.properties or production-shared.properties)

password.site.encoder=org.springframework.security.crypto.bcrypt.BCryptPasswordEncoder

For the bean overrides, the more recent versions of Broadleaf have moved to using Java Classes for configuration. That is supported in Spring and is a nicer way to configuration your application.

See https://docs.spring.io/spring-javaconfig/docs/1.0.0.m3/reference/html/creating-bean-definitions.html

For example, to override the LoginServiceImpl class, you would create an @Configuration class and add the bean. Note that here is already a SiteConfig.java class defined in the DemoSite project but you could add another @Configuration class if desired:

@Configuration
public class NewConfigurationClass {

    // The bean name is the method name (blLoginService)
    @Bean
    public LoginService blLoginService() {
      return new MyLoginService();
    }
}

You can have multiple beans defined in your configuration class.

You can revert to (or include) using an applicationContext.xml file, if you choose. You would simply add the following ImportResource to one of your @Configuration classes:

@ImportResource({"classpath*:applicationContext.xml"})

With that setup you could defined beans in Java or in xml. See https://www.javaguides.net/2018/09/spring-importresource-annotation-example.html

While this is certainly achievable, I would recommend you eventually migration to using the Java Config approach.