Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Jazz Team Server/RTC behind firewall with port routing

Hi,

We're running into issues with Jazz/RTC behind our firewall. On the server behind the firewall, Jazz runs on WAS, HTTPS port 9443. In the config files, WAS as well as Jazz is configured to use port 9443. We are able to access the server from our local network using port 9443. For ease of access we want it to be accessible from our domain, using port 443. So we set up our firewall to route external port 443 to internal 9443. Quite simple, daily stuff. But when we try to access the Jazz server using the domain link with port 443 we get three different situations:
1. Using the /jazz/admin link we get a message that we are not authorized to use the Jazz Team Server Admin UI. We have not had the ability to login however. This indicates that we are able to initially access the server, so the port is routed correctly from 443 to 9443.
2. Using the /jazz link we get a server timeout
3. Using the /jazz/web link we get a message that says "Loading..." but this stays there forever. Once again this indicates the the routing is correct.

We could of course setup WAS/Jazz to run on port 443 so port 443 external directly points to 443 internally (we've done that before and that works, also through our firewall) but this is not something we want to do.

I've got the feeling that there is some problem after an initial connection and therefor the traffic is disrupted. But I cannot figure out where and why.

Anyone got an idea?

0 votes



One answer

Permanent link
Interesting - we have a similar issue but are looking to keep the port the same externally and internally so that bookmarks and tool configs (e.g., RTC eclipse pluging) don't have to be changed as users go from an internal connection to an external one.


Hi,

We're running into issues with Jazz/RTC behind our firewall. On the server behind the firewall, Jazz runs on WAS, HTTPS port 9443. In the config files, WAS as well as Jazz is configured to use port 9443. We are able to access the server from our local network using port 9443. For ease of access we want it to be accessible from our domain, using port 443. So we set up our firewall to route external port 443 to internal 9443. Quite simple, daily stuff. But when we try to access the Jazz server using the domain link with port 443 we get three different situations:
1. Using the /jazz/admin link we get a message that we are not authorized to use the Jazz Team Server Admin UI. We have not had the ability to login however. This indicates that we are able to initially access the server, so the port is routed correctly from 443 to 9443.
2. Using the /jazz link we get a server timeout
3. Using the /jazz/web link we get a message that says "Loading..." but this stays there forever. Once again this indicates the the routing is correct.

We could of course setup WAS/Jazz to run on port 443 so port 443 external directly points to 443 internally (we've done that before and that works, also through our firewall) but this is not something we want to do.

I've got the feeling that there is some problem after an initial connection and therefor the traffic is disrupted. But I cannot figure out where and why.

Anyone got an idea?

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Feb 02 '10, 4:56 a.m.

Question was seen: 7,470 times

Last updated: Feb 02 '10, 4:56 a.m.

Confirmation Cancel Confirm