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

Uploading new PKCS#12 certificate credentials results in a 404

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • credentials-plugin
    • None
    • Credentials Plugin version 1337.v60b_d7b_c7b_c9f
      Jenkins version 2.456 on RHEL8
    • 2.459

      When uploading a credential of kind "Certificate", after selecting the "Certificate" option from the "Kind" dropdown and then clicking the "Upload PKCS#12 certificate" radio button, the Jenkins UI displays an "Oops - Not Found" error. See pkcs12-before-browse.png

      Browsing and selecting a certificate results in an error: "An internal error occurred during form field validation (HTTP 404). Please reload the page and if the problem persists, ask the administrator for help." See pkcs12-after-browse.png

      In the browser inspector, I can see one HTTP POST request with a 404 status code to the URL https://<JENKINS_URL>/manage/credentials/store/system/domain/_/'/descriptorByName/com.cloudbees.plugins.credentials.impl.CertificateCredentialsImpl$UploadedKeyStoreSource/checkUploadedKeystore.

      This issue is a blocker, as it blocks users from adding PKCS#12-type certificates to the credentials store.

        1. pkcs12-after-browse.png
          pkcs12-after-browse.png
          67 kB
        2. pkcs12-before-browse.png
          pkcs12-before-browse.png
          95 kB
        3. plugins.txt
          2 kB
        4. run-jenkins.sh
          0.9 kB

          [JENKINS-73166] Uploading new PKCS#12 certificate credentials results in a 404

          Mark Waite added a comment -

          Thanks very much for the bug report! I can duplicate the problem with Jenkins 2.456 but can't duplicate it with the release candidate build of Jenkins 2.452.1. I'm using the same version of the credentials plugin in both cases. In the case that I can duplicate it, I use the following steps:

          1. Create a plugins.txt file that lists the plugins and their versions
          2. Create a run-jenkins.sh script that downloads Jenkins 2.456 and the plugins specified in the plugins.txt file
          3. Run the run-jenkins.sh script and complete the setup wizard by creating a user account and choosing to install no additional plugins
          4. Open "Manage Jenkins" >> "Credentials" and create a new "Certificate" credential
          5. Confirm that clicking the "Upload PKCS#12 certificate" checkbox results in an "Oops not found" page but does not generate any stack trace in the console log

          I can duplicate the problem with Jenkins 2.453 and 2.454 but do not see the problem with weekly 2.452.

          Mark Waite added a comment - Thanks very much for the bug report! I can duplicate the problem with Jenkins 2.456 but can't duplicate it with the release candidate build of Jenkins 2.452.1. I'm using the same version of the credentials plugin in both cases. In the case that I can duplicate it, I use the following steps: Create a plugins.txt file that lists the plugins and their versions Create a run-jenkins.sh script that downloads Jenkins 2.456 and the plugins specified in the plugins.txt file Run the run-jenkins.sh script and complete the setup wizard by creating a user account and choosing to install no additional plugins Open "Manage Jenkins" >> "Credentials" and create a new "Certificate" credential Confirm that clicking the "Upload PKCS#12 certificate" checkbox results in an "Oops not found" page but does not generate any stack trace in the console log I can duplicate the problem with Jenkins 2.453 and 2.454 but do not see the problem with weekly 2.452.

          Mark Waite added a comment -

          I bisected the changes to Jenkins core between Jenkins 2.452 and Jenkins 2.453 and it seems that the issue is from commit 89c7754341 in pull request 9136.

          I've left a comment on that pull request asking the submitter of the pull request to review this issue report.

          Thanks again for reporting the issue cdekkers.

          Mark Waite added a comment - I bisected the changes to Jenkins core between Jenkins 2.452 and Jenkins 2.453 and it seems that the issue is from commit 89c7754341 in pull request 9136 . I've left a comment on that pull request asking the submitter of the pull request to review this issue report. Thanks again for reporting the issue cdekkers .

            Unassigned Unassigned
            cdekkers Cas Dekkers
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: