Jérôme, Just to make sure I understand -- if you use PHPCAS, without using mod_auth_cas, you experience the same redirect loop? Is the application using PHPCAS being accessed over HTTPS ?
The configuration directives for mod_auth_cas are all in the README, accessible here: https://github.com/jasig/mod_auth_cas Using mod_auth_cas, can you add both "CASDebug On" and "LogLevel DEBUG" to your Apache config, and send us the debug logs? Thank you, -Matt Matthew J. Smith University of Connecticut UITS [email protected] ________________________________________ From: Jérôme Benoit [[email protected]] Sent: Tuesday, April 24, 2012 3:18 PM To: [email protected] Subject: Re: [cas-user] CAS Server, Apache CAS and Reverse proxy Le Tue, Apr 24, 2012 at 04:11:52PM +0200, Jérôme Benoit a écrit: > > The pb seems to be a redirection loop between dev.asso-cocktail.org and > auth.asso-cocktail.org, it looks like either the reverse proxy forgot > to pass the correction URI extension or I fail to understand. > > What should be the correct full URI the browser should get after the > login screen ? I've bypassed the reverse proxy and I still have a redirection loop. So the pb is not the reverse proxy. Whatever the pb is, I fail to find it (and without any kind of list of configuration directives, it's far from easy). Wireshark do not help me either, the HTTP frames just show the redirection loop. I've CASified other application with PHPCAS, the redirection loop is also there so ... Cheers. -- Jérôme Benoit aka fraggle La Météo du Net - http://grenouille.com OpenPGP Key ID : 9FE9161D Key fingerprint : 9CA4 0249 AF57 A35B 34B3 AC15 FAA0 CB50 9FE9 161D -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
