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

No suitable binding handler for VaultAppRoleCredential.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Fixed but Unreleased (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Labels:
      None
    • Environment:
      K8S 1.18
      Jenkins: 2.277.2
      credentials-binding-plugin: 1.2.4
      Vault Harshicorp: 2.37.0
    • Similar Issues:

      Description

      We wantr to use roleid/secretid stored as credentials in Jenkins/Vault plugin as that will issue a Vault token that pipeline can then use to access Vault. Provisioned appId in Vault for the Jenkins Pipeline and then generated secretid. Next, populated roleID/SecretIDs as Jenkins-> Credentials->VaultRoleId (path kept default approle).

      Excerpt from the pipeline

      stage('Integration tests') {
      steps {
      withCredentials([[$class: 'VaultTokenCredentialBinding', credentialsId: "${env.VAULT_CREDENTIALS}", vaultAddr: "${env.VAULT_ADDR}", vaultNamespace: "serviceevents-dev1-kv/"]])

      { sh 'echo TOKEN=$VAULT_TOKEN' sh 'echo ADDR=$VAULT_ADDR' }

       

      Error thrown:

      No suitable binding handler could be found for type com.datapipe.jenkins.vault.credentials.VaultAppRoleCredential. Supported types are StandardUsernamePasswordCredentials,FileCredentials,StringCredentials,DockerServerCredentials,SSHUserPrivateKey.

      Any ideas? Suggestions on how to further troubleshoot or work it around? Thanks

        Attachments

          Activity

          peppe1977 Pedro Salomao created issue -
          peppe1977 Pedro Salomao made changes -
          Field Original Value New Value
          Description configured appId in Vault for the Jenkins Pipeline and then generated secretid. populate roleID/SecretIDs as Jenkins/Credentials/VaultRoleId (path kept default approle). Once executed the pipeline....relevant excerpt is below. We just want to use roleid/secretid stored as credentials in Jenkins/Vault plugin as that will issue a Vault token that pipeline can then use to access Vault.

          stage('Integration tests') {
                steps {
                  withCredentials([[$class: 'VaultTokenCredentialBinding', credentialsId: "${env.VAULT_CREDENTIALS}", vaultAddr: "${env.VAULT_ADDR}", vaultNamespace: "serviceevents-dev1-kv/"]]) {
                    sh 'echo TOKEN=$VAULT_TOKEN'
                    sh 'echo ADDR=$VAULT_ADDR'
                  } 

          Got this error: any ideas? pls advise

          No suitable binding handler could be found for type com.datapipe.jenkins.vault.credentials.VaultAppRoleCredential. Supported types are StandardUsernamePasswordCredentials,FileCredentials,StringCredentials,DockerServerCredentials,SSHUserPrivateKey.
          We wantr to use roleid/secretid stored as credentials in Jenkins/Vault plugin as that will issue a Vault token that pipeline can then use to access Vault. Provisioned appId in Vault for the Jenkins Pipeline and then generated secretid. Next, populated roleID/SecretIDs as Jenkins-> Credentials->VaultRoleId (path kept default approle).

          Excerpt from the pipeline

          stage('Integration tests') {
                steps {
                  withCredentials([[$class: 'VaultTokenCredentialBinding', credentialsId: "${env.VAULT_CREDENTIALS}", vaultAddr: "${env.VAULT_ADDR}", vaultNamespace: "serviceevents-dev1-kv/"]]) {
                    sh 'echo TOKEN=$VAULT_TOKEN'
                    sh 'echo ADDR=$VAULT_ADDR'
                  } 

          Error thrown:

          No suitable binding handler could be found for type com.datapipe.jenkins.vault.credentials.VaultAppRoleCredential. Supported types are StandardUsernamePasswordCredentials,FileCredentials,StringCredentials,DockerServerCredentials,SSHUserPrivateKey.

          Any ideas? Suggestions on how to further troubleshoot or work it around? Thanks
          peppe1977 Pedro Salomao made changes -
          Resolution Not A Defect [ 7 ]
          Status Open [ 1 ] Fixed but Unreleased [ 10203 ]

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            peppe1977 Pedro Salomao
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: