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

Credentials cannot be found by ARN when using custom clients

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When the custom clients feature is enabled, credentials use the secret ARN as their ID rather than the secret name.

      However when a job attempts to bind a credential that uses the secret ARN as its ID, the binding fails with an error along the lines of "could not find credential with the ID '<ARN>'".

      The same binding for the same credential works fine when the default client is used, so the credential uses the secret name instead.

        Attachments

          Activity

          Hide
          chriskilding Chris Kilding added a comment -

          In the absence of general namespacing capabilities for credentials, ARNs are the only mechanism available to us to let secrets from multiple accounts (potentially with the same name) coexist with each other. If credentials aren't able to bind using ARNs then this will put the brakes on multi-account support (JENKINS-63183, JENKINS-63184, JENKINS-59670 and others), and we'll have to remove that beta feature.

          Show
          chriskilding Chris Kilding added a comment - In the absence of general namespacing capabilities for credentials, ARNs are the only mechanism available to us to let secrets from multiple accounts (potentially with the same name) coexist with each other. If credentials aren't able to bind using ARNs then this will put the brakes on multi-account support ( JENKINS-63183 , JENKINS-63184 , JENKINS-59670 and others), and we'll have to remove that beta feature.
          Show
          chriskilding Chris Kilding added a comment - Moved to  https://github.com/jenkinsci/aws-secrets-manager-credentials-provider-plugin/issues/71

            People

            Assignee:
            chriskilding Chris Kilding
            Reporter:
            chriskilding Chris Kilding
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: