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

Password option is not getting updated in Chrome

      Here's a request from one of our internal users:

      I am facing an issue in Jenkins. I have created a job and using perforce for “source code management”. For the first time I have entered wrong password in perforce under SCM and saved the job, it got failed.

      Later When I enter new password and save the job It works fine, But after editing the job again it’s taking the initial wrong password. So I have to have to save the password every time I am editing the job.

          [JENKINS-23164] Password option is not getting updated in Chrome

          Rob Petti added a comment -

          How does this user know that the password is being reset? Does the job fail again or are they just assuming that the password is wrong because the displayed length is different?

          Rob Petti added a comment - How does this user know that the password is being reset? Does the job fail again or are they just assuming that the password is wrong because the displayed length is different?

          Oleg Nenashev added a comment -

          The job fails again.
          Unfortunately, the Job-config history had been wiped by retention policies when I've got the request

          Oleg Nenashev added a comment - The job fails again. Unfortunately, the Job-config history had been wiped by retention policies when I've got the request

          Rob Petti added a comment -

          It's worth noting that we have several unit tests that cover this case. I suspect it's some issue with his browser saving the password.

          Rob Petti added a comment - It's worth noting that we have several unit tests that cover this case. I suspect it's some issue with his browser saving the password.

          Oleg Nenashev added a comment -

          Seems so.
          Unfortunately, I don't have Chrome on my PC.

          Probably, I'll install&debug the issue later. It is not critical [for me], because Chrome is not officially supported by our services

          Oleg Nenashev added a comment - Seems so. Unfortunately, I don't have Chrome on my PC. Probably, I'll install&debug the issue later. It is not critical [for me] , because Chrome is not officially supported by our services

          Rob Petti added a comment -

          FWIW, I used chrome for everything, and I've never run into this issue. I believe quite strongly that this is simply user error, and that they have inadvertently saved the password in their browser.

          Rob Petti added a comment - FWIW, I used chrome for everything, and I've never run into this issue. I believe quite strongly that this is simply user error, and that they have inadvertently saved the password in their browser.

          Daniel Beck added a comment -

          Rob: Right, the problem is that saving the login page credentials shouldn't cause job credentials to be changed. (Or cause the browser to ask whether to save credentials on every job config page with password specified for that matter!)

          In fact, all other credentials in Jenkins shouldn't probably prevent autocompletion by default to circumvent this issue. I've seen related reports by others as well.

          Daniel Beck added a comment - Rob: Right, the problem is that saving the login page credentials shouldn't cause job credentials to be changed. (Or cause the browser to ask whether to save credentials on every job config page with password specified for that matter!) In fact, all other credentials in Jenkins shouldn't probably prevent autocompletion by default to circumvent this issue. I've seen related reports by others as well.

          Oleg Nenashev added a comment -

          Confirmed. The scenario with a cached password reproduces the issue.
          /lib/form/password should be fixed. I'll find/create the appropriate issue.

          BTW, I propose to apply a workaround in Perforce Plugin in order to avoid the issue on legacy Jenkins cores.

          Oleg Nenashev added a comment - Confirmed. The scenario with a cached password reproduces the issue. /lib/form/password should be fixed. I'll find/create the appropriate issue. BTW, I propose to apply a workaround in Perforce Plugin in order to avoid the issue on legacy Jenkins cores.

          Daniel Beck added a comment -

          Apparently some browsers now ignore the option to not autofill passwords, see JENKINS-28474 and JENKINS-22338.

          Daniel Beck added a comment - Apparently some browsers now ignore the option to not autofill passwords, see JENKINS-28474 and JENKINS-22338 .

          Oleg Nenashev added a comment -

          I'll unlikely be able to work on this again - snowed under the stuff forever

          Oleg Nenashev added a comment - I'll unlikely be able to work on this again - snowed under the stuff forever

            Unassigned Unassigned
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: