nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Software 8.10.1 behind Reverse Proxy doesn't work

Joan Williamson

A Reverse Proxy environment was set up for our Jira dev/test application but it is not working. I created another connector in the server.xml file for the Reverse Proxy connection and Jira was restarted. The reverse proxy team set up an environment for us as well. I don't know what that configuration really entails though.

I login to the RP environment and click the link for Jira and successfully get the Jira login screen presented. But when I enter my credentials, Jira actually logs me in but immediately returns to the RP page with the Jira link. If I click the link again and try to login, it indicates that I am already authenticated. So, after the first login attempt it does log me in but does not proceed to the dashboard page. Does anyone have any idea what could be missing?

Accepted answers

Nic Brough -Adaptavist-

Without knowing what your proxy is, the best we can do is confirm what you have set up on the Jira side should work.

Is your "base url" set to the address the proxy presents to the clients? (This one should not break your login, but would cause other issues, so it's worth knowing if you do have it to hand)
What, exactly, does the connector the proxy uses say? This is the section in the <jira install>/conf/server.xml that starts with connector (please do obscure anything that you might worry about revealing in public)
What, exactly, does the context path attribute say?
Are you using SSL or not?

As an example of the sort of info I'm looking for here, copied and pasted (and obscured) from a working Jira behind an SSL proxy

Base url: https://reddwarf.jupitermining.corp/jira
Connector: <Connector port="8081" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>"
maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false" secure="true" scheme="https"
proxyName="reddwarf.jupitermining.corp" proxyPort="443"/>
Context: <Context path="/jira" docBase="${catalina.home}/atlassian-jira" rel.....
SSL: Yes

All comments

Pramodh M

Hi @Joan Williamson

Please contact your team for more information on the proxy and can we know what proxy you are using.

Here's the KB link for described issues as well
https://confluence.atlassian.com/jirakb/keep-getting-redirected-to-login-page-after-logging-in-user-s-login-token-got-rejected-upon-logging-in-800863634.html

Thanks,
Pramodh

Pramodh M

FYI
https://confluence.atlassian.com/jirakb/login-screen-loops-back-to-login-screen-with-no-error-when-using-correct-username-and-password-874784386.html

Joan Williamson

I was informed that our proxy is custom software - no apache or IIS.

Pramodh M

Has the team followed instructions from this URL
https://confluence.atlassian.com/jirakb/configure-an-outbound-proxy-for-use-in-jira-server-247857187.html

Please check with the server.xml file from the give link here
https://confluence.atlassian.com/jirakb/keep-getting-redirected-to-login-page-after-logging-in-user-s-login-token-got-rejected-upon-logging-in-800863634.html

Nic Brough -Adaptavist-

Without knowing what your proxy is, the best we can do is confirm what you have set up on the Jira side should work.

Is your "base url" set to the address the proxy presents to the clients? (This one should not break your login, but would cause other issues, so it's worth knowing if you do have it to hand)
What, exactly, does the connector the proxy uses say? This is the section in the <jira install>/conf/server.xml that starts with connector (please do obscure anything that you might worry about revealing in public)
What, exactly, does the context path attribute say?
Are you using SSL or not?

As an example of the sort of info I'm looking for here, copied and pasted (and obscured) from a working Jira behind an SSL proxy

Base url: https://reddwarf.jupitermining.corp/jira
Connector: <Connector port="8081" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>"
maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false" secure="true" scheme="https"
proxyName="reddwarf.jupitermining.corp" proxyPort="443"/>
Context: <Context path="/jira" docBase="${catalina.home}/atlassian-jira" rel.....
SSL: Yes

Joan Williamson

Yes, the base url is set properly.

Connector: <Connector port="8443" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>"
maxThreads="150" minSpareThreads="25" connectionTimeout="60000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="org.apache.coyote.http11.Http11NioProtocol" useBodyEncodingForURI="true"
acceptCount="10" disableUploadTimeout="true" secure="true" scheme="https"
proxyName="my.company.com" proxyPort="443"/>
Context: <Context path="" docBase="${catalina.home}/atlassian-jira" rel.....
SSL: Yes

Nic Brough -Adaptavist-

Ok, there's absolutely nothing wrong on the Jira side of your settings.

So I am afraid it is the proxy setup. It sounds like it is doing half the job, in that it is passing https://my.company.com requests back to the Jira server, but I do not think it is returning everything it should in the other direction.

It's taking you back to its own landing page instead of doing the (reverse)proxy in full.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server