Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-20764

Attempting to download an artifact or build log using "curl + personal access token" returns nothing and the command succeeds

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 9.5.0
    • Artifacts
    • None
    • 117

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      The new authentication with the personal access token is not working when we attempt to download an artifact or build log with curl.

      Steps to Reproduce

      1. Create a plan with a shared artifact
      2. Run a build
      3. Create a personal access token with full access for a Bamboo admin user
      4. Try to download the artifact with the following command:
      curl -H "Authorization: Bearer <ACCESS_TOKEN>" \
     -X GET '<BAMBOO_URL>/browse/<BUILD-KEY>/artifact/shared/<ARTIFACT_NAME>/<ARTIFACT_FILE>' > <ARTIFACT_FILE>

      Expected Results

      The artifact will be download or the command will fail.

      Actual Results

      The artifact is not downloaded and the command succeeds

      Workaround

      Use plain text authentication (user + password).

      curl --user <USER>:<PASSWORD>
     -X GET '<BAMBOO_URL>/browse/<BUILD-KEY>/artifact/shared/<ARTIFACT_NAME>/<ARTIFACT_FILE>' > <ARTIFACT_FILE>

       

            [BAM-20764] Attempting to download an artifact or build log using "curl + personal access token" returns nothing and the command succeeds

            arthurnunesq added a comment - - edited

            I'm baffled that I'm not able to download Bamboo artifacts through a script using the personal access token. 
            It's kinda unbelievable.

             

            As mentioned previously, Bamboo should just accept personal access tokens as passwords, like other tools do (e.g. JFrog Artifactory).

            arthurnunesq added a comment - - edited I'm baffled that I'm not able to download Bamboo artifacts through a script using the personal access token.  It's kinda unbelievable.   As mentioned previously, Bamboo should just accept personal access tokens as passwords, like other tools do (e.g. JFrog Artifactory).

            YGG IT added a comment -

            This is a total blocker for us. Also a workaround shouldnt be to use a clear text username and password. That just seems like the wrong way to go!

            YGG IT added a comment - This is a total blocker for us. Also a workaround shouldnt be to use a clear text username and password. That just seems like the wrong way to go!

            saper added a comment -

            we couldn't use the Username + token combination as a work around.

            There is another enhancement request already related to this:

            https://jira.atlassian.com/browse/BAM-20641 Bamboo authentication tokens should be acceptable as a password

            saper added a comment - we couldn't use the Username + token combination as a work around. There is another enhancement request already related to this: https://jira.atlassian.com/browse/BAM-20641 Bamboo authentication tokens should be acceptable as a password

            Saurabh Singh added a comment -

            Hi team, we really need this on priority basis to be implemented.

            Saurabh Singh added a comment - Hi team, we really need this on priority basis to be implemented.

            Jagan Kattaru added a comment -

            What about when completly disable the Basic Authentication for REST API calls in this we couldn't use the Username + token combination as a work around.

            and its really a blocker for us and users are getting frustated as they were not able to download the artifacts from bamboo using REST API call.

            Do we have any work around?

            Jagan Kattaru added a comment - What about when completly disable the Basic Authentication for REST API calls in this we couldn't use the Username + token combination as a work around. and its really a blocker for us and users are getting frustated as they were not able to download the artifacts from bamboo using REST API call. Do we have any work around?

            Shafeequr Rehman Mohammed added a comment -

            +1

            Shafeequr Rehman Mohammed added a comment - +1

            Karthik added a comment -

            This is very important to us, we made changes to download artifacts using the personal access token, later realized, downloaded artifacts were incomplete.

            Karthik added a comment - This is very important to us, we made changes to download artifacts using the personal access token, later realized, downloaded artifacts were incomplete.

            Thorsten Klein added a comment -

            pbruski / 2cd4b6cecf0f: is there any update on this? We would also really welcome this feature

            Thorsten Klein added a comment - pbruski / 2cd4b6cecf0f : is there any update on this? We would also really welcome this feature

            Aaron Campecino added a comment -

            I need this feature for my requirements. Please implement.

            Aaron Campecino added a comment - I need this feature for my requirements. Please implement.

            Johnny Sheppard added a comment - - edited

            I would also find this very helpful

            Johnny Sheppard added a comment - - edited I would also find this very helpful

              851f15845f55 Mateusz Szmal
              dsantos Daniel Santos (Inactive)
              Votes:
              51 Vote for this issue
              Watchers:
              40 Start watching this issue

                Created:
                Updated:
                Resolved: