You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems in Grails 3.3.10 the order of plugin initialisation is changed even if loadAfter = ['springSecurityCore'] is set, so the springSecurityService bean is not detected in AuditLoggingGrailsPlugin some times.
Therefore, the DefaultAuditRequestResolver is initialized instead of the SpringSecurityRequestResolver
Workaround for now is to manually register the SpringSecurityRequestResolver in resources.groovy.
Seems in Grails 3.3.10 the order of plugin initialisation is changed even if loadAfter = ['springSecurityCore'] is set, so the springSecurityService bean is not detected in AuditLoggingGrailsPlugin some times.
Therefore, the DefaultAuditRequestResolver is initialized instead of the SpringSecurityRequestResolver
Workaround for now is to manually register the SpringSecurityRequestResolver in resources.groovy.
The text was updated successfully, but these errors were encountered: