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

The Jenkins P4 Plugin offers two ways to store credentials: passwords and tickets. Both use the Jenkins built-in Credentials Manager. The customer needs to store the credentials in Conjur Plugin instead.

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • p4-plugin
    • None

      Here it is description from the customer;
      ###############################
      The Jenkins P4 Plugin offers two ways to store credentials: passwords and tickets. Both use the Jenkins built-in Credentials Manager. We need to store the credentials in Conjur instead. Our Conjur Plugin allows us to inject secrets into the build as environment variables, but something more is needed to get Conjur to work with the P4 Plugin. Please advise.Cisco's Build Environment Security program now requires keeping a single "secret zero" in the Jenkins Credential Manager. This stores an API key to a Conjur namespace. All other secrets must go into this namespace. We use a Jenkins plugin to map these secrets into Jenkins job environment variables.
      ###############################

            Unassigned Unassigned
            kpark_perforce Kevin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: