firewall problems with RM (requirements management)

Terry Little (11●1●5) | asked Dec 01 '16, 5:45 p.m.

We have CLM set up on Linux with Websphere front end. We have a URL set up that listens on port 443 and does port forwarding to our servers. we can get to the JTS application without a problem. However, when we try to get to rm (requirements management) to authenticate, it redirects to the jts/oath internal port and not 443 and it blocked at the firewall. Has anyone else had this experience? How was it solved? We are not allowed to start the processes on port 443 internaly.

One answer

Most liked answers ↑|Newest answers|Oldest answers

permanent link

Dominic Tulley (381●1●4) | answered Dec 06 '16, 1:26 p.m.

Hi Terry,
The issue could be that your RM server has the JTS server set up as a friend using the internal port instead of the 443 port.
If you go to /rm/admim, choose the "application" page and look at the Friends (Outbound) entries you can check this.

thanks
-Dominic

Comments

Donald Nong commented Dec 06 '16, 10:16 p.m. | edited Dec 06 '16, 10:16 p.m.

The other way to check this is look for the "com.ibm.team.repository.server.jts.url" property in the RM teamserver.properties file. It should be the same as the "com.ibm.team.repository.server.webapp.url" property in the JTS teamserver.properties file. Basically, that's the "public URI" of JTS.

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.

It's all about the answers!

Related questions

firewall problems with RM (requirements management)

One answer

Your answer