Using WGET or another method to download Bamboo shared artifacts (6.10.4+)

timofey_shklyarov

https://confluence.atlassian.com/bamboo/personal-access-tokens-976779873.html

https://community.atlassian.com/t5/Bamboo-questions/Re-Using-WGET-or-another-method-to-download-Bamboo-artif/qaq-p/1256940/comment-id/26919#M26919 

After upgrading to 6.10.4 - not able to download shared artifacts using curl any more.

Previously used -u user:password. Now it stopped working, though no notification about it in Bamboo KB..

Tried using save-cookies method and token as well..

curl -v -H "Authorization: Bearer XXXXXXXXXXXXXXXX" https://bamboo.domain.com/artifact/HTMLAI-HAI1401/shared/build-204/htmlai.war/htmlai.war 
...
> GET /artifact/HTMLAI-HAI1401/shared/build-204/htmlai.war/htmlai.war HTTP/1.1 
> Host: bamboo.domain.com 
> User-Agent: curl/7.66.0 
> Accept: */* 
> Authorization: Bearer XXXXXXXXXXXXXXXXXXXXX 
> 
* Mark bundle as not supporting multiuse 
< HTTP/1.1 302 
< X-ASEN: SEN-11111
< X-Frame-Options: SAMEORIGIN 
< X-Content-Type-Options: nosniff 
< Location: https://bamboo.domain.com/userlogin!doDefault.action?os_destination=/artifact/HTMLAI-HAI1401/shared/build-204/htmlai.war/htmlai.war 


curl -v -u 'user:password' https://bamboo.domain.com/artifact/HTMLAI-HAI1401/shared/build-204/htmlai.war/htmlai.war 
...
* Server auth using Basic with user 'user' 
> GET /artifact/HTMLAI-HAI1401/shared/build-204/htmlai.war/htmlai.war HTTP/1.1 
> Host: bamboo.domain.com 
> Authorization: Basic XXXXXXXXXXXX
> User-Agent: curl/7.66.0 
> Accept: */* 
> 
* Mark bundle as not supporting multiuse 
< HTTP/1.1 401 
< X-ASEN: SEN-111111
< X-Frame-Options: SAMEORIGIN 
< X-Content-Type-Options: nosniff 
< X-Seraph-LoginReason: AUTHENTICATION_DENIED 

Any suggestions?

 

Daniel Santos_157bm4

Hi @timofey_shklyarov

Thank you for all the details shared. They are very helpful!

 

Accessing with user and password (plain text credentials)

According to my tests, on Bamboo 6.10.4, I get the 401 error when using the wrong credentials (incorrect user or password). The reason for your error could be the same or even a different one.

I get the 403 error when the permissions are incorrectly set to allow plan access. Either the user does not have access to the instance through global permissions (could be logged in user's permission) or he does not have access to the project or plan affected.

What I want to say with the above sentences is that I was able to successfully use the old authentication method to download the artifact with curl.

 

Accessing with a personal access token

I was not able to download the artifact using this method. I just registered a bug about this since I get a successful code when running the curl command but I don't get any file stream.

This is the bug I just opened:

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

 

Next steps

• Can you double-check if you are able to access the artifact through the UI using that pair of user credentials?
• If you can access that through the UI, would you be able to try running the curl command from the server terminal using its IP to check if it will work when the request comes from the same IP of the server?

I'll wait for your next comments.