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

p12 path not saving in credentials.xml

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Labels:
      None
    • Environment:
    • Similar Issues:

      Description

      .p12 file not recordings in credentials.xml and empty(has size 0 bytes (placed in folder \gauth))

      Steps to reproduce:
      1) install google-oauth-plugin
      2) go to Jenkins Dashboard
      3) login as Administrator
      4) go to Credentials
      5) Select "Global credentials (unrestricted)"
      6) Select "Add Credentials"
      7) Kind - Google Service account from private key
      8) Provide any "Project Name"
      9) Select option "P12 key"
      10) Fill "E-Mail Address"
      11) provide p12 key
      12) press "ok"
      13) Look into credentials.xml in Jenkins home folder

      • e-mail for project filled, but no path to p12 key
        14) Check size of p12 key in folder "gauth"
      • size of p12 key is 0 bytes

      On Jenkins installed in Debian 8 by deb file all works fine.

        Attachments

          Activity

          Hide
          orrc Christopher Orr added a comment -

          Another Windows user on the mailing list also reported having this problem:
          https://groups.google.com/forum/#!msg/jenkinsci-users/7kj4UxDmFfU/oNfEx0JOBQAJ

          Show
          orrc Christopher Orr added a comment - Another Windows user on the mailing list also reported having this problem: https://groups.google.com/forum/#!msg/jenkinsci-users/7kj4UxDmFfU/oNfEx0JOBQAJ
          Hide
          orrc Christopher Orr added a comment -

          Another Windows user contacted me today with the same issue.

          I suggested the workaround of manually overwriting the $JENKINS_HOME\gauth\key<whatever>.p12 file with the contents of the actual .p12 file.

          Based on the timing of user reports, I'd guess this bug was introduced in version 0.4 of the Google OAuth plugin, but I don't currently have time (or a Windows machine) to investigate further...

          Show
          orrc Christopher Orr added a comment - Another Windows user contacted me today with the same issue. I suggested the workaround of manually overwriting the $JENKINS_HOME\gauth\key<whatever>.p12 file with the contents of the actual .p12 file. Based on the timing of user reports, I'd guess this bug was introduced in version 0.4 of the Google OAuth plugin, but I don't currently have time (or a Windows machine) to investigate further...
          Hide
          orrc Christopher Orr added a comment -

          The same user let me know that overwriting the $JENKINS_HOME\gauth\key<whatever>.p12 file manually didn't seem to work.

          However, downgrading to version 0.3 of the plugin did work.

          Show
          orrc Christopher Orr added a comment - The same user let me know that overwriting the $JENKINS_HOME\gauth\key<whatever>.p12 file manually didn't seem to work. However, downgrading to version 0.3 of the plugin did work.
          Show
          craigbarber Craig Barber added a comment - Migrated to: https://github.com/jenkinsci/google-oauth-plugin/issues/41

            People

            Assignee:
            astroilov Andrey Stroilov
            Reporter:
            ssic7i Serhii Sheiko
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: