Reverse proxy and URI rewrite

Hi all.

We have JIRA service desk on 'cloud' and I have set Nginx reverse proxy along with URI rewrite, the point is to have mycompanyname.atlassian.net rewriten to our company domain.

I've managed to get almost everything working, passing on the cookies as well, but I keep getting 403 for:

POST /rest/analytics/1.0/publish/bulk

So the login isn't working, I just get redirected to the same page.

Was getting 401 before setting up cookie proxy (atlassian.xsrf.token, JSESSIONID...).

I'm proxying from HTTPS(Nginx) to HTTPS(Tomcat), our A record is alive and SSL cert is fine, no problems there.

Can you please provide more info on the conditions why am I getting 403 from Atlassian Nginx or what needs to be set to mitigate this issue.

Thank you in advance.

2 answers

1 accepted

1 vote
Accepted answer

The 403 was related to Referer header, still problems with sign in as  the X-AUSERNAME header response stays 'anonymous'  after the actual login.

Same thing when reverse proxying with Apache 2.4. - anonymous x-ausername and loads the login page again.

Got official reply that Atlassian cloud apps don't support reverse proxying.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,807 views 18 22
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you