Hi, I'm having some trouble getting CAS to work properly in a proxy-type configuration. I'm getting HTTP 502.3 (Bad Gateway) errors. I was wondering if anyone's run into this before and/or if there is an obvious answer.
I've got Tomcat listening for HTTP traffic on 8080 with CAS running on http://mymachine:8080/cas/ (accessibly only internally) I've got IIS 7.5 running with the Web Farm framework proxying requests for https://mymachine/cas to http://mymachine:8080/cas/ (port 443 is open externally). I'm trying to have IIS handle the SSL and not have to open multiple ports on the firewall for the different web servers. I'm trying to integrate with the https://mymachine/cas/ URL from the .NET CAS Client in another folder on the machine (e.g., https://mymachine/someapp/). Requests are getting kicked over to https://mymachine/cas/login which is what I want, but when I attempt to login to the CAS server, I get a 502.3 Bad Gateway error with an EOF error behind the scenes. I'm wondering if there is anything I need to tell Tomcat or CAS configuration-wise that might get around the problem. Btw, mymachine is just a placeholder for a valid, fully qualified domain name with a trusted SSL certificate. Tomcat logs aren't showing any errors at all. Everything seems to be working properly except that the ticket validation never occurs. Thanks, -Scott -- 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-dev
