Hey Jérôme, There is actually a service parameter (I accidentally did not add it on my previous mail): https://ec2-22-22-222-22.compute-1.amazonaws.com: 8443/cas/login?service=http%3a%2f%2f domu-11-11-11-11-11-11.compute-1.internal%2fapp1
As you can see, it is the private amazon dns that is being forwarded, so i guess the problem actually starts here. I tried adding 'CASRootProxiedAs' to '/etc/apache2/https.conf' but then it failed on restarting the apache2 service, saying is is not familiar with 'CASRootProxiedAs'. Apparently my 'mod_cas_auth' version was 1.0.8 while 'CASRootProxiedAs' is supported on 1.0.9 +. This is why I didnt know of 'CASRootProxiedAs' directive at the first place (is wanst listed on 1.0.8 README file :) ). So I reinstalled the module with a higher version and it all worked out. Problem solved!!! Thanks man !! On Sun, Jun 3, 2012 at 3:09 PM, jleleu <[email protected]> wrote: > Hi, > > The behaviour of the CAS server is pretty simple : after successfull > authentication, the user is redirected to the CAS service which is the url > given as the service input parameter of the /login url. > In your case, I don't see any service parameter for the /login url. What > is the value of the service parameter (/login url) ? > Is it a public or an internal url ? > > In case of internal url, I think you could use the CASRootProxiedAs > parameter in the mod_auth_cas configuration to force the public host. > > Best regards, > Jérôme > > -- > 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 > -- * Ronen Itkin* Taykey | www.taykey.com -- 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
