Details
-
Bug
-
Resolution: Fixed
-
Low
-
5.14.3.1
-
Severity 3 - Minor
-
0
-
Description
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.
Attachments
Issue Links
- is duplicated by
-
-
- Closed
-
- was cloned as
-
-
- Long Term Backlog
-
- has action
-
BDEV-12527 Loading...