Securing Bamboo with Apache using SSL
If you want to set up SSL access to Bamboo, follow steps 1 to 4 below. When you are finished, users will be able to make secure connections to Apache HTTP Server; connections between Apache HTTP Server and Bamboo will remain unsecured (not using SSL).
- The steps on this page would normally be performed after Integrating Bamboo with Apache HTTP Server.
- It would be possible to set up an SSL connection between Apache HTTP Server and Tomcat (Bamboo), but that configuration is very unusual, and not recommended in most circumstances.
Step 1: Configure the Tomcat Connector for SSL
Find the normal (non-SSL)
Connector directive in Tomcat's
server.xml file, and change the
proxyPort attributes as follows:
redirectPort directive causes Tomcat-initiated redirections to secured resources to use the specified port. Right now, the Bamboo configuration of Tomcat does not involve Tomcat-initiated redirections, so the change to
redirectPort is redundant. Nevertheless, we suggest that you change it as directed above for the sake of completeness.
Step 2: Set up a virtual host in Apache HTTP Server
Un-comment the following LoadModule directive in Apache HTTP Server's
LoadModule ssl_module modules/mod_ssl.so
Add the following directives to the
Listen 443 <VirtualHost *:443> SSLEngine On SSLCertificateFile "/usr/local/apache2/conf/server.crt" SSLCertificateKeyFile "/usr/local/apache2/conf/server.key" ProxyPass / http://localhost:8085/ connectiontimeout=5 timeout=300 ProxyPassReverse / http://localhost:8085/ </VirtualHost>
Listen directive instructs Apache HTTP Server to listen for incoming requests on port 443. Actually, we could omit that directive in this case, since Apache HTTP Server listens for
https requests on port 443 by default. Nevertheless, it's good to make one's intentions explicit.
VirtualHost directive encloses a number of child directives that apply only and always to requests that arrive at port 443. Since our
VirtualHost block does not include a
ServerName directive, it inherits the server name from the main server configuration.
SSLEngine directive toggles the use of the SSL/TLS Protocol Engine. In this case, we're using it to turn SSL on for all requests that arrive at port 443.
SSLCertificateFile directive tells Apache HTTP Server where to find the PEM-encoded certificate file for the server.
SSLCertificateKeyFile directive tells Apache HTTP Server where to find the PEM-encoded private key file corresponding to the certificate file identified by the
SSLCertificateFile directive. Depending on how the certificate file was generated, it may contain a RSA or DSA private key file, making the
SSLCertificateKeyFile directive redundant; however, Apache strongly discourages that practice. The recommended approach is to separate the certificate and the private key. If the private key is encrypted, Apache HTTP Server will require a pass phrase to be entered when it starts up.
For more information about the support for SSL in Apache HTTP Server, refer to the Apache SSL/TLS Encryption manual. In addition, you will find lots of relevant information in the
<apache directory>/conf/extra/httpd-ssl.conf file, which is included in the standard Apache distribution.
Step 3: Create SSL certificate and key files
In Step 2, you specified
server.key as the certificate file and private key file respectively. Those two files must be created before we can proceed. This step assumes that OpenSSL is installed on your server.
Generate a server key file:
openssl genrsa -des3 -out server.key 2048
You will be asked to provide a password. Make sure that the password is strong because it will form the one real entry point into the SSL encryption set-up. Make a note of the password because you'll need it when starting Apache HTTP Server later.
Generate a certificate request file (
openssl req -new -key server.key -out server.csr
Generate a self-signed certificate (
openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt
The above command generates a self-signed certificate that is valid for one year. You can use the certificate signing request to purchase a certificate from a certificate authority. For testing purposes though, the self-signed certificate will suffice. Copy the certificate file and private key file to the locations you specified in Step 2.
cp server.key /usr/local/apache2/conf/ cp server.crt /usr/local/apache2/conf/
Step 4: Update the base URL for 'https'
Open a browser window and log into Bamboo using an administrator account. Go to the Bamboo administration area and click Server s ettings (under 'Settings'). Change Base URL to use 'https'.
Using a self-signed certificate
There are two implications of using the self-signed certificate:
- When you access Bamboo in a web browser, you can expect a warning to appear, alerting you that an un-trusted certificate is in use. Before proceeding you will have to indicate to the browser that you trust the certificate.
- When you perform a git clone operation, SSL verification will fail.
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed while accessing
GIT_SSL_NO_VERIFYenvironment variable. In Unix, you can set the variable in-line with git commands as follows:
GIT_SSL_NO_VERIFY=true git clone