Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-2186

Salted password cannot be set through CLI for Elytron filesystem-realm identity

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 3.0.0.Alpha20
    • 3.0.0.Alpha16
    • CLI
    • None
    • Hide

      Start server with standalone-elytron.xml and run following CLI commands:

      /subsystem=elytron/filesystem-realm=fsrealm:add(path=/tmp/fsrealm)
      /subsystem=elytron/filesystem-realm=fsrealm/identity=admin:add()
      /subsystem=elytron/filesystem-realm=fsrealm/identity=admin:set-password(bcrypt={iteration-count=42,password=passwrod1,salt=bytes{0x31,0x32,0x33}})
      {
          "outcome" => "failed",
          "failure-description" => "WFLYCTL0155: password may not be null",
          "rolled-back" => true
      }
      
      Show
      Start server with standalone-elytron.xml and run following CLI commands: /subsystem=elytron/filesystem-realm=fsrealm:add(path=/tmp/fsrealm) /subsystem=elytron/filesystem-realm=fsrealm/identity=admin:add() /subsystem=elytron/filesystem-realm=fsrealm/identity=admin:set-password(bcrypt={iteration-count=42,password=passwrod1,salt=bytes{0x31,0x32,0x33}}) { "outcome" => "failed" , "failure-description" => "WFLYCTL0155: password may not be null " , "rolled-back" => true }

      Password encryption/hash mechanisms which contain salt attribute for filesystem-realm identity cannot be added through CLI. set-password operation fails and finishes with failure-description "WFLYCTL0155: password may not be null" even if password was set. It seems when salt attribute with bytes value is used then password attribute is ignored by CLI.

      Following password encryption/hash mechanisms from filesystem-realm identity are affected by issue:

      • bcrypt
      • salted-simple-digest

            jdenise@redhat.com Jean Francois Denise
            olukas Ondrej Lukas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: