--On 22 May 2007 11:35 -0700 webzo <[EMAIL PROTECTED]> wrote:
> > > This is not directly related to CAS but something I am seeing while deploying > CAS and I am trying to find out if others have faced a similar issue- > Basically, there are 2 webapps (say), webapp_1 and cas. > 1. User tries to go to http://mydomain:8080/webapp_1 > 2. User gets redirected to > https://mydomain:8443/cas/login?service=http://mydomain:8080/webapp_1 > 3. User authenticates successfully > 4. User is redirected to http://mydomain:8443/webapp_1 > > So, incase you didn't catch it- after successful authentication, the browser > appears to be attempting to redirect the user back to the original > application (webapp_1) but on the wrong port (8443). I've never known CAS to interfere with the service URL you pass at login - it would be quite a problem if particular browser versions could inspire that behaviour. I have known CAS to redirect to service URLs on port 8080 and for those applications to decide they need to be secure and redirect again to 8443. Are you certain the redirect to 8443 is being done by CAS and not by webapp_1? Is a ticket being generated? Can you check the server logs to see if the ticket is being validated? Dave ---------------------- David Spencer Information Systems and Computing University of Bristol _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
