Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-28699

Password type parameterized fields get bogus auto-population of default value despite empty field on job save

      Password type parameters on parameterized jobs are being automatically populated despite having the default value set blank. If I have not filled the field, then it should NOT be filling itself. This occurs in any browser regardless of auto-complete settings, and the value is some hash I've definitely never put in a field, so I am quite sure it isn't the browsers' fault.

          [JENKINS-28699] Password type parameterized fields get bogus auto-population of default value despite empty field on job save

          Gordon Pettey added a comment -

          The default value being forced is the crypt/hash of the passphrase from the first global credential (an ssh key).

          Gordon Pettey added a comment - The default value being forced is the crypt/hash of the passphrase from the first global credential (an ssh key).

          Gil Shinar added a comment - - edited

          I thought I have found a workaround. Removing the defaultValue element line from the parameter in the config.xml and reloading jenkins' configuration from disk solves this issue for the first rerun. After entering a value to the first run, it becomes the default value to next runs.

          Gil Shinar added a comment - - edited I thought I have found a workaround. Removing the defaultValue element line from the parameter in the config.xml and reloading jenkins' configuration from disk solves this issue for the first rerun. After entering a value to the first run, it becomes the default value to next runs.

            huybrechts huybrechts
            petteyg359 Gordon Pettey
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: