SEC-1240: {ssha} is specified in the Spring Security password-encoder schema, but isn't handled by code #1488

spring-issuemaster opened this Issue Sep 8, 2009 · 2 comments

1 participant


Peter Mularien (Migrated from SEC-1240) said:

Pretty minor, but I noticed that the {ssha} option for LDAP SSHA is an allowable value in the schema for password-encoder's hash attribute, but it isn't handled by PasswordEncoderParser.


Peter Mularien said:

Sorry, I butchered the syntax for code formatting. {ssha} is the actual value that is specified in the XML schema and not supported by the PasswordEncoderParser.


Luke Taylor said:

I've added an extra mapping to PasswordEncoderParser. The same class is used for both {sha} and {ssha}, so in practice there isn't any difference.

@spring-issuemaster spring-issuemaster added this to the 3.0.0 RC1 milestone Feb 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment