The cas.properties file also has the urls for your server. Maybe there is something else inside the apache virtual host that is getting in the way? I've used the same backend Tomcat servers with different hostnames and ssl certs on the Apache instance. The only thing I've had to set to prevent the url from changing is the proxyName setting. I have found that everything works best when the /cas path is used everywhere.
Pat On Fri, May 1, 2009 at 4:39 PM, Micah Baker <[email protected]>wrote: > Thanks for the tips...I tried using proxyHost and proxyPort (found online a > reference to proxyName and tried that too) but the URL still starts off > correctly and then drops the FQDN after you click login. > > This appears to be a javascript issue during the POST command. I managed > to catch the source after a failed POST and saw that the action of the > submit button was: <form id="fm1" class="fm-v clearfix" > action="//cas/login?SAMLRequest=fVJLT8M..." > > This indicates that it is being generated by the javascript somewhere > incorrectly. Since I am unfamiliar with the structure of CAS I'm not sure > where to fix this. My tinkering indicates that it is in the > common_rosters.js file but it is too complicated for me to feel comfortable > changing. > > Thanks, > > Micah > -- > 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 > -- 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
