Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to enable CORS on Bamboo?

I would like to take advantage of the Bamboo APIs, but when I make requests from my client application, I get a CORS error (it seems to me that CORS requests should automatically be enabled for the Bamboo API). How can I allow my origin access to the Bamboo APIs?

2 answers

Most of the stuff said in here: https://answers.atlassian.com/questions/69356

Should work in your case also.

This gave me a lot of grief. But I was finally able to figure out the magic Apache settings to solve this in an Apache proxy:

 

<VirtualHost _default_:443>
        ServerName yourhost
        ServerAdmin someperson@yourorg.com

        SSLEngine on
        SSLCertificateFile /etc/ssl/private/yourorg.com.crt
        SSLCertificateKeyFile /etc/ssl/private/yourorg.com.key
        SSLCertificateChainFile /etc/ssl/private/chain.pem

        SSLProxyEngine          On
        ProxyRequests           Off
        ProxyPreserveHost       On

        RewriteEngine On
        RewriteCond %{REQUEST_METHOD} OPTIONS
        RewriteRule ^(.*)$ - [ENV=PREFLIGHT:true]

        SetEnvIf Origin "^(.*)$" ORIGIN=$0
        Header always set Access-Control-Allow-Origin %{ORIGIN}e env=PREFLIGHT
        Header always set Access-Control-Allow-Credentials "true" env=PREFLIGHT
        Header always set Access-Control-Allow-Methods "POST, GET, OPTIONS" env=PREFLIGHT

        RewriteCond %{REQUEST_METHOD} OPTIONS
        RewriteRule ^(.*)$ $1 [R=204,L]

        ProxyPass / http://host.yourorg.com:8087/
        ProxyPassReverse / http://host.yourorg.com:8087/
</VirtualHost>

This allows Apache to intercept preflight requests (that are sent as an OPTIONS request) and add some headers (only if it is an OPTIONS request) and then return a 204.

The rest of it is just enabling to CORS filter in Tomcat: https://tomcat.apache.org/tomcat-8.0-doc/config/filter.html#CORS_Filter.

In which file, on Windows if anyone knows, should the above content be placed in?  Excluding the Tomcat CORS filter, are there any additional steps required to enable CORS for Bamboo?

 

Thanks! 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

244 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you