Broker URL Setting for Remote Agents over SSL

matt_dolan_advantasure_com May 9, 2018

Hi-  We have a new Bamboo Server running 6.4 and have installed a remote agent on a nearby server.  We have a requirement for the Bamboo server to connect to the remote agent over SSL.  Am seeing errors on the remote agent server that might indicate the Broker URL setting is awry. 

What is the recommended Broker URL and Broker Client URL setting when connecting to remote agent over SSL?

We have tried for Broker URL a setting of

 ssl://<ip address of bamboo server>:443?wireFormat.maxInactivityDuration=300000

and

ssl://<domain name of bamboo server>:443?wireFormat.maxInactivityDuration=300000  (In this case bamboo actually appends the IP address after the domain name somehow)

Neither of those work.  The remote agent logs seem to indicate that Bamboo agent does not like the Broker URL setting(s)

 

On a previous HTTP  installation we had tcp://0.0.0.0:54663.....  SSL was not configured for this, however.

Thanks!

 

1 answer

0 votes
Gabriel Ribeiro
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 9, 2018

Hi @matt_dolan_advantasure_com

You must keep the same address:port and change only the protocol.

As stated in the Securing your remote agents documentation, these are the steps you should follow:

  1. Shut down your Bamboo server and agents.
  2. Change the protocol of your Broker URL and Broker client URL in the bamboo.cfg.xml file to 'SSL'. Note, do not change the address of this URL.<property name="bamboo.jms.broker.uri">ssl://myhost:myport</property><property name="bamboo.jms.broker.client.uri">failover:(ssl://myhost:myport)</property>
  3. Start up the Bamboo server.
  4. Start up the Bamboo agents. If your agents do not start up, please check that you have set up your certificates correctly.

If bamboo is over HTTPS, please also make sure you have the following parameters on the catalina connector in the <installation directory>/conf/server.xml file

            scheme="https"
            proxyName="<bamboo BASE URL>"
            proxyPort="443"

 thanks

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events