RTC Public URI & reverse proxy
Hi, We have the following situation: RTC has a public URI of https://jts.internal:9443/ccm Due to security reasons and VPN policies some of the RTC users need to use other URLs in order to get access to RTC - e. g. https://location1:9443/ccm or https://location2:9443/ccm
So we installed a reverse proxy (Apache2/Tomcat). In most of the cases it works fine - but from time to time when the user clicks some buttons or links in the web ui https://jts.internal:9443/ccm is used instead of the given URI for this Location.
Is this a known limitation or is there a work around for this situations?
Best regards
Alexander
|
Accepted answer
|
Hi,
That´s the same story that I told the customer - this was just to double check it!
Best regards Alexander
Ralph Schoon selected this answer as the correct answer
|
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.
Comments
For all I know, the scenario you describe is not supported. The requests always need to go to the public URI that is selected for the system. The server knows itself under this public URI and will use that public URI root to identify its resources. So for various actions, you will receive back the public URI, instead of the URI you used. You also don't want the alternative URI used for the request getting coded into any artifacts.
I remember we tried this "multiple URL approach" for customers and it was not doable.
So as far as I can tell, you should use a VPN solution that separates the users without the need to change the access URI.
If you use a proxy solution, where the proxy is configured specifically under the covers and the requests are sent to that proxy without changing the URI and thus being transparent to the Jazz application, this should work as well.
I deliberately put this as a comment, to keep it unanswered. Maybe there is someone out there that knows different.