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

Improve Bamboo EC2 Wizard to initially setup proxy settings in server.xml

XMLWordPrintable

      Problem Definition

      The Bamboo EC2 wizard sets up an apache reverse proxy in front of Bamboo that handles SSL and forwards internally to the tomcat listener on 8085. However, it doesn't setup the tomcat proxy attributes in /media/atlassian-data/installs/bamboo/atlassian-bamboo-5.xx.x/conf/server.xml:

      proxyName="ec2-xx-xxx-xxx-xxx.yyyyyyyyyy.compute.amazonaws.com"
proxyPort="443"
scheme="https"
secure="true"
      • proxyName should be set to the Public DNS.

      Full connector example:

      <Connector
            protocol="HTTP/1.1"
            port="8085"

            maxThreads="150" minSpareThreads="25"
            connectionTimeout="20000"
            disableUploadTimeout="true"
            acceptCount="100"

            enableLookups="false"
            maxHttpHeaderSize="8192"

            useBodyEncodingForURI="true"
            URIEncoding="UTF-8"

            redirectPort="8443"
            proxyName="ec2-xx-xxx-xxx-xxx.yyyyyyyyyy.compute.amazonaws.com"
            proxyPort="443"
            scheme="https"
            secure="true"
            />

      Suggested Solution

      While this might be slightly redundant as users will more than likely have to change this at some point once they setup their DN, it would be great if the wizard set these attributes up initially so we don't hit XSRF errors out of the box.

            [BAM-18063] Improve Bamboo EC2 Wizard to initially setup proxy settings in server.xml

            Daniel Saravia added a comment -

            It also applies to v8.1.3 when using a domain with SSL, thank you.

            Daniel Saravia added a comment - It also applies to v8.1.3 when using a domain with SSL, thank you.

            Jeremy Owen added a comment -

            Thanks glotov.artyom1370540834. I've updated it and added the clarification that proxyName should be set to your Public DNS.

            Jeremy Owen added a comment - Thanks glotov.artyom1370540834 . I've updated it and added the clarification that proxyName should be set to your Public DNS.

            Artem Glotov added a comment -

            Hi, all!

            I have little fix to the bug description:

            except (from the request tag in log message)
            proxyName="ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com"
            should be (from the origin/referrer tag):
            proxyName="ec2-xx-xxx-xxx-xxx.yyyyyyyyyy.compute.amazonaws.com"
            where yyyyyyyyyy = Amazon region subdomain (e.g. us-west-2).

            It works for me. If you agree, please, fix the bug description.

            Artem Glotov added a comment - Hi, all! I have little fix to the bug description: except (from the  request tag in log message ) proxyName="ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com" should be (from the origin/referrer  tag): proxyName="ec2-xx-xxx-xxx-xxx.yyyyyyyyyy.compute.amazonaws.com" where yyyyyyyyyy = Amazon region subdomain (e.g. us-west-2). It works for me. If you agree, please, fix the bug description.

              moles Marcin Oles
              jowen@atlassian.com Jeremy Owen
              Affected customers:
              4 This affects my team
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: