OAuth config on Bamboo trying to access 127.0.0.1:8085?

Robert Hanson July 8, 2016

I am tying to use Application Links to link an internal Bamboo instance with Jira cloud.  I add the link in Jira, it does the redirection to Bamboo, and then it errors out in Bamboo.

The root of the problem is that the Incoming Authentication and Outgoing Authentication panels in Bamboo show broken pages within the iframe.  The issue appears to be that the iframes are trying to load content from http://127.0.0.1.

E.g. http://127.0.0.1:8085/plugins/servlet/applinks/auth/conf/oauth/add-consumer-by-url/...

I have verified that the Base URL on the General Configuration screen is correct.  It is using the URL of the Apache server that sits in front of Bamboo (which is using named virtual hosts).

The Apache config looks ok to me, but here is it.

<VirtualHost *:80>

    ServerName mybambooserver.com

    ErrorLog logs/bamboo-error_log

    CustomLog logs/bamboo-access_log common

    ProxyRequests OFF

    <Location />

        ProxyPass http://127.0.0.1:8085/

        ProxyPassReverse http://127.0.0.1:8085/

        Order allow,deny

        Allow from all

    </Location>

</VirtualHost>

 

It feels like there is some other configuration change that needs to be made in Bamboo.

 

Here is what it looks like in Bamboo.

Screen Shot 2016-07-08 at 11.54.36 AM.png

1 answer

1 accepted

0 votes
Answer accepted
Robert Hanson July 9, 2016

The solution is to add the hostname and proxy port to the <Connector> in conf/server.xml

&lt;Connector
   ...
   proxyName="mybambooserver.com"
   proxyPort="80"
   /&gt;

 

It seems weird that Bamboo has you set a Base URL so that all of the links work properly, but then doesn't use it when creating Application Links.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events