[email protected] wrote:
Patrick, I'm still CAS beginner; please take the following with a grain
of salt:
Are you sure that you have your ServerName directive set properly in
httpd.conf? I believe that is what mod_auth_cas uses for the service
parameter in its redirect and it seems to think that the ServerName is
set to fglast2.stanford.edu:
https://glast-ground.slac.stanford.edu/cas/login?service=http%3a%2f%2fgl
ast2.stanford.edu%2fCAS%2f
Thanks for this. It led me to the answer, albeit a bit indirectly.
The stray f in that URL is actually part of %2f, which is the
hexadecimal representation of the / character.
I decided to see if my own internal redirection was causing the problem.
As the readers may remember, I had this in my top directory:
RewriteEngine on
RewriteCond %{HTTP_HOST} !^www-glast.stanford.edu [NC]
RewriteCond %{HTTP_HOST} !^$
RewriteRule (.*) http://www-glast.stanford.edu/$1 [L,R]
The idea is that no matter which of my server's names is used, the
request would be redirected to www-glast.stanford.edu, which is
also Apache's ServerName. I want people to get used to using that
name, even though the name glast2 has been exposed and some people
keep using it.
So I added another condition
RewriteCond %{REQUEST_URI} !^\/CAS
which prevents the redirection when looking at the directory where I
set up mod_auth_cas authentication.
This has been a valuable learning experience, and when I get to the
real implementation it should go more smoothly. Thanks to you and to
Phil Ames.
--
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
