Marty, David,

Thanks for the replies...

We are using a Cornell developed SSO called CUWebAuth, and adding the tomcatAuthentication="false" directive did the trick. Transparent login working beautifully 400 (soon to be 4000) happy users.

Thanks,
Karel

At 09:50 AM 2/26/2006, you wrote:
In your connector config in server.xml add tomcatAuthentication="false". This will allow the auth info from Apache through.

Karel Sedlacek wrote:
Is there something I need to do in order to make sure that Tomcat is passing along REMOTE_USER? I have a Hyperion report server installation that we want to convert to using transparent logon using delivered CGI macros $REMOTE_USER$ and $TRUSTEDPASS$. When I reconfigure the Authentication service to use the macros, and hit the URL protected by our SSO mechanism the behavior appears as though REMOTE_USER is not populated. Apache is definitely passing the header attribute as we use it extensively on this site for non-Tomcat applications. Help! Thanks!

Karel Sedlacek                                          [EMAIL PROTECTED]
CIT Data Administration                                 Phn 607-255-7742
Cornell University Fax 607-255-1297
Ithaca, NY 14853


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
David Smith
Network Operations Supervisor
Department of Entomology
Cornell University
2132 Comstock Hall
Ithaca, NY 14853
Phone: (607) 255-9571
Fax: (607) 255-0940


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Karel Sedlacek                                          [EMAIL PROTECTED]
CIT Data Administration                                 Phn 607-255-7742
Cornell University Fax 607-255-1297 Ithaca, NY 14853


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to