JIRA and Confluence Behind Apache SSL Reverse Proxy

This is just a quick note about running Atlassian JIRA and Confluence behind Apache HTTPD using the strong reverse proxy and SSL features of the full Apache web server. This helps simplify your SSL configuration by keeping the certificate settings out of the Atlassian (Tomcat) app bundles. The reverse proxy allows us to serve both Jira and Confluence under the same hostname/port using different app context paths (like “/jira” and “/confluence”). If each app demands more resources than the single OS can handle, you can expand the reverse proxy config to support load balancing across multiple app servers, or just to host each app on a different back-end server. NOTE that these examples are provided ONLY for viewing/discussion and should NOT be used for configuring your own systems. All configuration changes to your Atlassian servers and services should be based on official Atlassian support documents and other Atlassian support channels.

We’ll start with the front-end, a sample snippet from Apache HTTPD web server. Important Apache 2.2 directives include: ProxyPreserveHost, ProxyPass, and ProxyPassReverse.

Now let’s review config changes to “server.xml” for JIRA to support the reverse proxy. Important changes include the path attribute of Context element, and several attributes under the 8080 Connector element: proxyName, proxyPort, and scheme.

The next sample file is a typical “server.xml” from Confluence to support the reverse proxy. Changes are basically the same as JIRA – path attribute of Context element, and several attributes under the 8090 Connector element: proxyName, proxyPort, and scheme.

Advertisements

About notesbytom

Keeping technology notes on WordPress.com to free up my mind to solve new problems rather than figuring out the same ones repeatedly :-).
This entry was posted in Linux, System Administration and tagged , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s