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

Support for Jenkins credential storage

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Rather than configuring each build with an API key and secret, we should be able to globally configure a key and secret as a credential in Jenkins. This should be used by default for every build, with the option to override under an 'Advanced' button.

        Attachments

          Activity

          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Antonio Mansilla
          Path:
          README.md
          pom.xml
          src/main/java/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusNotifier.java
          src/main/java/org/jenkinsci/plugins/bitbucket/api/BitbucketApi.java
          src/main/resources/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusNotifier/config.jelly
          src/main/resources/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusNotifier/global.jelly
          src/main/resources/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusNotifier/help-credentialsId.html
          src/main/resources/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusNotifier/help-globalCredentialsId.html
          http://jenkins-ci.org/commit/bitbucket-build-status-notifier-plugin/faae72c4f1cbd72552955376c479e23649fa6e00
          Log:
          Merge pull request #12 from Flagbit/add-credentials-management

          JENKINS-32574 Add credentials management

          Compare: https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin/compare/d73ec91ad424...faae72c4f1cb

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Antonio Mansilla Path: README.md pom.xml src/main/java/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusNotifier.java src/main/java/org/jenkinsci/plugins/bitbucket/api/BitbucketApi.java src/main/resources/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusNotifier/config.jelly src/main/resources/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusNotifier/global.jelly src/main/resources/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusNotifier/help-credentialsId.html src/main/resources/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusNotifier/help-globalCredentialsId.html http://jenkins-ci.org/commit/bitbucket-build-status-notifier-plugin/faae72c4f1cbd72552955376c479e23649fa6e00 Log: Merge pull request #12 from Flagbit/add-credentials-management JENKINS-32574 Add credentials management Compare: https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin/compare/d73ec91ad424...faae72c4f1cb
          Hide
          sagayd Sagayaraj David added a comment -

          Antonio,
          In Access Control Security Realm, you choose Active Directory and input values with subdomain.domain1.com,subdomain.domain2.com. In this case, API token is not working, but cleartext password seems to be working.

          Show
          sagayd Sagayaraj David added a comment - Antonio, In Access Control Security Realm, you choose Active Directory and input values with subdomain.domain1.com,subdomain.domain2.com. In this case, API token is not working, but cleartext password seems to be working.
          Hide
          flagbit Antonio Mansilla added a comment -

          Hi Sagayaraj David sorry but I'm testing the plugin with a clean jenkins installation and I can't find any section in the jenkins configuration or credentials where appears something like "Access Control Security Realm" or "Active Directory". I guess that is because you have some additional plugins installed.

          I will set this issue as resolved as the basic credential management is supported and already merged to be released in the next plugin version. So I'd wait until the next release, test it again with the new plugin version and in case the problem is still persisting please create a new issue and provide more information about your setup like jenkins version, plugins involved...

          Thank you very much for your colaboration

          Show
          flagbit Antonio Mansilla added a comment - Hi Sagayaraj David sorry but I'm testing the plugin with a clean jenkins installation and I can't find any section in the jenkins configuration or credentials where appears something like "Access Control Security Realm" or "Active Directory". I guess that is because you have some additional plugins installed. I will set this issue as resolved as the basic credential management is supported and already merged to be released in the next plugin version. So I'd wait until the next release, test it again with the new plugin version and in case the problem is still persisting please create a new issue and provide more information about your setup like jenkins version, plugins involved... Thank you very much for your colaboration
          Hide
          sagayd Sagayaraj David added a comment - - edited

          Hello Antonio,

          Yes we had to install Active Directory plugin. Enable Security. In the security database, we have different options to choose from including Jenkins Own Database and Active Directory. When we have choosen Active Directory and the value is single domain lik domainname.com, the API calls via scripted clients like wget http://jenkins.domain.com/api/xml. it is working good. However when we two+ domains in the domain field of Active Directory, the API token is not recognized in the scripted client calls. Reponds with authentication failure

          If this belongs to different section, can you please create a ticket and track it

          Show
          sagayd Sagayaraj David added a comment - - edited Hello Antonio, Yes we had to install Active Directory plugin. Enable Security. In the security database, we have different options to choose from including Jenkins Own Database and Active Directory. When we have choosen Active Directory and the value is single domain lik domainname.com, the API calls via scripted clients like wget http://jenkins.domain.com/api/xml . it is working good. However when we two+ domains in the domain field of Active Directory, the API token is not recognized in the scripted client calls. Reponds with authentication failure If this belongs to different section, can you please create a ticket and track it
          Hide
          epowell Evan Powell added a comment -

          Global OAuth credentials are working great for me. Thank you for a great easy to use plugin!

          Show
          epowell Evan Powell added a comment - Global OAuth credentials are working great for me. Thank you for a great easy to use plugin!

            People

            • Assignee:
              flagbit Antonio Mansilla
              Reporter:
              epowell Evan Powell
            • Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: