Reverse proxy and URI rewrite

[Deleted user]

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.

[Deleted user · Accepted solution]

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

[Deleted user]

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

[Deleted user]

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