How to create a Tomcat unproxied connector (backdoor)

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Does this apply to you?

When needing to access specific nodes in a Jira DC Cluster, it is necessary to have a separate Tomcat connector, without using the LB as proxy for access.

Example scenario


  • Proxied address:
  • Unproxied address:


You must be able to browse to the application via the unproxied URL. Some network configurations may allow communication between the two servers, but you must be able to browse to the unproxied addresses for the purpose of creating the application link.

Set up an unproxied HTTP connector in Tomcat

To bypass a reverse proxy or SSL configuration, introduce an additional HTTP connector in Tomcat. The following is a bare minimum HTTP connector for use in Tomcat across Atlassian Products:

<Connector port="8081" connectionTimeout="20000" maxThreads="200" minSpareThreads="10"
    enableLookups="false" acceptCount="10" URIEncoding="UTF-8" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`&quot;&lt;&gt;" />

To make use of this, edit the server.xml file for the application in question. The connector must be added inside the Service element. You will also need to restart the application to take effect.

You should adjust the value of the port attribute in the new connector. Ensure to use a port that isn't already used by any application on the same physical machine. For example, if you have JIRA listening for incoming connections on port 8080 (which is in turn connected to a reverse proxy), you should change your new connector to something else, such as 8081.

If web.xml has been edited as per our documentation to redirect to SSL, the following lines will need to be removed:For more information, please see this Jira specific KB article.

Note for SSO bypass

The SSO configuration may need to be bypassed in order to log in to the node directly without redirection to SSO URL.  See this page for instructions:

Bypass SAML authentication for Jira Data Center


When testing for use cases, it may be necessary to connect to a specific node, without disrupting normal usage for your instances.

ProductJira, Confluence, Bitbucket, Bamboo, Fisheye
PlatformServer, Data Center
Last modified on Sep 21, 2021

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.