Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 

Excerpt
hiddentrue

For Apache and IIS it is described on pages 3-4 of the IOPLEX Jespa Operators Manual and is mentioned in our install instructions. The page from Atlassian - Integrating JIRA with NGINX, can serve as a reference for general configuration of NGINX when used with Atlassian products.

1
2
3
4
5
6
7
8
9
10
11
12
13
server {
    listen www.atlassian.com:80;
    server_name www.atlassian.com;
    location /jira {
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Jespa-Connection-Id $remote_addr:$remote_port;
        proxy_pass http://jira-hostname:8080/jira;
        client_max_body_size 10M;
        large_client_header_buffers  4 32k;
    }
}

Page Details Macro
titleHow to configure NGINX as reverse proxy so SSO works

 

Once you reconfigured your NGINX this way the telltale sign of it working will be in jespa.log at log level 4 - see *bold values*, showing the remote client's IP address and port as opposed to proxy's one. Some values have been obscured with ****

...