Redirect to crowd url

[cmbollareddy]

Hi.,

I have migrated and upgraded crowd (from 2.11.2 to 4.0.0V) from old to new server.

For users access purpose, I have updated the user directories with http://IPAddress:8095/crowd/ in JIRA, Confluence, Bitbucket and Bamboo.

Old Server URL: https://tech.prod.companyname.com/crowd/

Now, I’m planning to redirect Old server URL to new server and  permanently shutdown the old server.

Can you please suggest us. How to redirect the same URL from old to new server.

[LynnG]

You should not use an HTTP redirect for Crowd application integration. Instead, keep the same old public URL and make it point to the new Crowd server, usually by DNS change or reverse proxy/load balancer routing.

Your target should be:

Plain Text

1

https://tech.prod.companyname.com/crowd/

2

`

Show more lines

continuing to serve the new Crowd 4.0.0 instance.

Recommended approach

1. Point the old DNS name to the new server

Update DNS or load balancer so:

Plain Text

1

tech.prod.companyname.com

Show more lines

resolves/routes to the new Crowd server.

This is better than asking Jira, Confluence, Bitbucket, and Bamboo to use:

Plain Text

1

http://IPAddress:8095/crowd/

2

``

Show more lines

because Atlassian apps are sensitive to base URL, proxy, and XSRF/origin consistency. Atlassian’s Crowd proxy guidance says Crowd’s base URL should match the proxy name configured in server.xml. [support.at...assian.com]

---

2. Configure Crowd’s Base URL back to the old public URL

In Crowd 4, set the base URL to:

Plain Text

1

https://tech.prod.companyname.com/crowd/

Show more lines

Atlassian’s Crowd NGINX proxy document says that for normal Crowd operation, the base URL should match the proxyName value configured in server.xml, and in Crowd 3.0 and later this can be configured from Cog icon > General. [support.at...assian.com]

---

3. Configure Tomcat server.xml on the new Crowd server

Edit:

Plain Text

1

<crowd-install>/apache-tomcat/conf/server.xml

Show more lines

For HTTPS through a proxy/load balancer, your connector should include something like:

XML

1

<Connector port="8095"

2

protocol="HTTP/1.1"

3

connectionTimeout="20000"

4

redirectPort="8443"

5

URIEncoding="UTF-8"

6

scheme="https"

7

proxyName="tech.prod.companyname.com"

8

proxyPort="443" />

Show more lines

Atlassian’s Crowd NGINX proxy example shows adding proxyName, proxyPort, and scheme to the Tomcat connector, with the proxy name matching the public host used by users. [support.at...assian.com]

Then restart Crowd.

---

4. Configure reverse proxy or load balancer

If using NGINX, conceptually it should proxy the public Crowd URL to the new server:

Nginx Config

1

server {

2

listen 443 ssl;

3

server_name tech.prod.companyname.com;

4

5

location /crowd/ {

6

proxy_pass http://NEW_CROWD_IP:8095/crowd/;

7

proxy_set_header Host $host;

8

proxy_set_header X-Real-IP $remote_addr;

9

proxy_set_header X-Forwarded-For $remote_addr;

10

proxy_set_header X-Forwarded-Proto https;

11

proxy_redirect off;

12

}

13

}

Show more lines

Atlassian’s Crowd NGINX article shows proxying requests to Crowd’s internal Tomcat port and setting headers such as Host, X-Real-IP, and X-Forwarded-For. [support.at...assian.com]

---

5. Add the proxy as a trusted proxy in Crowd

If Crowd is behind a proxy, configure Crowd to trust the proxy server. Atlassian explains that when a proxy forwards a request, trusted proxy configuration lets Crowd recognize the original client IP rather than only the proxy’s IP. [confluence...assian.com]

In Crowd:

Plain Text

1

Crowd Administration Console > Trusted proxy servers

Show more lines

Add the proxy/load balancer IP or hostname.

---

6. Update Jira, Confluence, Bitbucket, and Bamboo back to the public Crowd URL

In each application’s Crowd user directory configuration, use:

Plain Text

1

https://tech.prod.companyname.com/crowd/

Show more lines

rather than:

Plain Text

1

http://IPAddress:8095/crowd/

2

``

Show more lines

This keeps one stable Crowd URL for browser access, REST calls, and application integrations.

Important warning

Do not rely on a simple 301 or 302 redirect from:

Plain Text

1

https://tech.prod.companyname.com/crowd/

Show more lines

to:

Plain Text

1

http://IPAddress:8095/crowd/

Show more lines

That can cause problems with authentication, cookies, XSRF checks, SSL expectations, and application integration. Atlassian notes that XSRF issues can occur when the request origin does not match the target, and recommends using the exact base URL and correct proxy settings. [support.at...assian.com]

Summary

Best setup:

Plain Text

1

Jira / Confluence / Bitbucket / Bamboo

2

|

3

v

4

https://tech.prod.companyname.com/crowd/

5

|

6

v

7

Reverse proxy / Load balancer / DNS

8

|

9

v

10

New Crowd server: http://NEW_CROWD_IP:8095/crowd/

Show more lines

After this works, you can permanently shut down the old server.