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

            Renata Dornelas made changes -
            Remote Link Original: This issue links to "Page (Atlassian Documentation)" [ 254394 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 1636765 ] New: JAC Bug Workflow v3 [ 3385975 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Jeremy Owen made changes -
            Description Original: h3. 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}}:
            {code}
            proxyName="ec2-xx-xxx-xxx-xxx.yyyyyyyyyy.compute.amazonaws.com"
            proxyPort="443"
            scheme="https"
            secure="true"
            {code}
            * {{proxyName}} should be set to the Public DNS.

            h3. 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.             		New: h3. 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}}:
            {code}
            proxyName="ec2-xx-xxx-xxx-xxx.yyyyyyyyyy.compute.amazonaws.com"
            proxyPort="443"
            scheme="https"
            secure="true"
            {code}
            * {{proxyName}} should be set to the Public DNS.

            Full connector example:
            {code}
            <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"
                        />
            {code}

            h3. 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.

            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Jeyanthan I (Inactive) made changes -
            Link New: This issue was cloned as BAM-19994 [ BAM-19994 ]
            Pawel Skierczynski made changes -
            Link New: This issue is duplicated by BAM-18805 [ BAM-18805 ]
            Marcin Oles made changes -
            Fix Version/s New: 6.2.3 [ 75226 ]
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            Marcin Oles made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            Marcin Oles made changes -
            Assignee New: Marcin Oles [ moles ]

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

                Created:
                Updated:
                Resolved: