Hello Christopher The redirection is in my hands.
If I edit /etc/httpd/conf/httpd.conf: JkMount / worker1 I'm sent to Tomcat home page (root level /) ---> /TOMCAT_HOME/webapps/ And the special headers are comming. But... if I edit /etc/httpd/conf/httpd.conf: JkMount /RS/* worker1 Trying to be send to my webApp ---> /TOMCAT_HOME/webapps/RS/ I'm sent to my webApp( /RS ) BUT !!! in this case I lose the special headers. PloP !!! Do you have any idea where I have to focus ? -------------------------------------------------------------------- | Now I put SSO (SiteMinder) to my app, for that I had to use apache, | because the SSO work with apache. Okay, so SiteMinder adds headers to requests that match certain criteria. | When I go there, I'm authenticated and if everything is ok (with my | user/pass) | this SSO add some extra-headers like this: | header=SM_USER=w024461 | header=SM_USERDN=uid=W024461,ou=People,dc=bankone,dc=net Can you get those headers in Tomcat? Or, are you saying that your can observe the request while still in Apache? | That mean, the extra-headers that SiteMinder (SSO) is putting in | the request are coming to Tomcat. Untils here all is ok. Sounds like Tomcat /is/ getting the headers. | But now I don't know what configuration I should do it | if I wanna be re-direct to mi wepApp; | http://sscllinuxora03.santiago.cl.jpmorganchase.com:8084/RS | passing the extra-headers without lossing them. You cannot pass HTTP headers through a redirect, not matter what configuration you use. The headers must be added with each request. That means that, after a redirect, SiteMinder has to re-add the headers to the new request. Thus, the redirect is not relevant to your problem. | Need I make some configurations on: | /home/tigger/jakarta-tomcat-5.0.28/webapps/RS/WEB-INF/web.xml | or: | /home/tigger/jakarta-tomcat-5.0.28/conf/server.xml You should not have to do anything to these files at all. Are you sure that SiteMinder is modifying the requests that ultimately go to Tomcat? -------------------------------------------------------------------- ----------------------------------------- This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities.
