What are mandatory header parameters required to login to ccm RTC server
Hi This is neel from Daimler development team , working for engineering portal application , Engineering portal provides proxy capabilities for internal daimler applications (similar to reverse proxy), RTC is one of the application need to be proxied in Engineering Poratl (i.e EngP) , when we access the rtc from browser https://daimler.zazz.example.com:9443/ccm , i am able to see the login page. (it works perfectly) but when external user comes through engp . (engp is internet facing application , we provide a link for rtc in engP application for external users access) https://daimler.supplier.example.com/EnginnerinProxy/app/RTC which we map inside our code to https://daimler.zazz.example.com:9443/ccm . when i verified the request / response trace between browser and engp are different , some header information is missing , when i send the request through our proxy code (we are using apache httpclient to send request to RTC through our code) . the login page is not getting loaded. could you please help me to understand what are the mandatory header information we need to send to ccm server while login into RTC. |
One answer
Hello
I have some questions: 1)what software is the portal running in order to perform like a proxy? 2) is this IHS+WAS as described here: https://jazz.net/wiki/bin/view/Deployment/ConfigureCLMEnterpriseReverseProxy RTC / CCM server needs to be called by the proxy or by a browser with the public URI that it was configured with during setup. For example, RTC could have been configured on the appserver as https://clm.example.org:9443/ccm. A proxy, such as the one in the article above, could be configured to redirect incoming requests to https://clm.example.org/ccm to the RTC app on the appserver at https://clm.example.org:9443/ccm. Note that in the above article, it does mention the need to "Force WAS to honor host headers" or else there is a redirect problem at the proxy stage. This is done through some custom properties at the appserver console, in this case WAS. See https://jazz.net/wiki/bin/view/Deployment/ConfigureCLMEnterpriseReverseProxy#4_Force_WAS_to_honor_host_header I don't know what this does under the covers. It's just part of the configuration for IHS+WAS to avoid a problem with Jazz redirecting to :xxxx ports on the IHS Server (where xxx is the port specific to the example in the article, i.e. 9443). You may also benefit from reading https://jazz.net/wiki/bin/view/Deployment/ConfigureCLMEnterpriseReverseProxyWithApache Lastly, for more information, read TN0013: Jazz Team Server Authentication Explained This tech note on the Jazz.net site (registration required) explains the authentication mechanism used by IBM Rational Jazz Team Server and the rationale for the design. It also describes how to change the configuration to use alternate authentication methods and to unsecure feed URLs for a custom deployment, along with the tradeoffs associated with each configuration. |
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.