Spring Security
  1. Spring Security
  2. SEC-1240

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

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: 3.0.0 M2
    • Fix Version/s: 3.0.0 RC1
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Activity

        Hide
        Peter Mularien added a comment -

        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.

        Show
        Peter Mularien added a comment - 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.
        Hide
        Luke Taylor added a comment -

        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.

        Show
        Luke Taylor added a comment - 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.

          People

          • Assignee:
            Luke Taylor
            Reporter:
            Peter Mularien
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: