This message was deleted.

I probably won't have any helpful answers, but there is a chance I might have a question or two that helps... • Are you confident you have the same

grails.plugin.springsecurity.password.algorithm = 'SHA-256'

for both versions? • You may want to check the plugin versions, and see if spring security changed libraries (or significant versions), as I believe the plugin relies heavily on standard

spring security

Have you checked the

conf/spring/resources.groovy

in both versions? I have:

// Place your Spring DSL code here
beans = {
    userPasswordEncoderListener(UserPasswordEncoderListener)
}

Perhaps that helps get you to the next step in debugging?

yes @seanoc5 ,I'm using the same

grails.plugin.springsecurity.password.algorithm = 'SHA-256'

for the same version but the spring security core in my build.gradle is not same for 3.3.9 the spring -security core version is 3.3.1 and for 5.3.2 i'm using 5.3..

Spring Security 5, used by the Grails Spring Security plugin, changed the way that passwords are encoded. You can create a custom DelegatingPasswordEncoder to support both old and new formats concurrently, and/or do a simple database migration to move all passwords to the new format. We have created the custom encoder and have a subsequent update planned so there will be no downtime while both old and new versions of the app are running in our production environment. https://grails.github.io/grails-spring-security-core/latest/index.html https://www.baeldung.com/spring-security-5-password-storage https://dzone.com/articles/password-encoder-migration-with-spring-security-5

Thanks @Joe Kocina, Going through the links and check for both the possibilities.