The example doesn't have it because its hard-coded into the XML configuration file (as long as it wasn't removed).
If your application is successfully redirecting to /cas/login?service= http://www.service.com then the *only* way it could not be redirecting back is if the casLoginView.jsp was modified to not submit the service parameter with the POST. Otherwise, any exception would rely in the fact that the service parameter as never passed to the login page (which generally can only result if the login page url is misconfigured). Is the url for this application publicly available? I can try and login (and fail since I don't have access) but I should be able to see the urls. You can email me the url directly if its available if you don't want the url publicly archived. Thanks -Scott On 2/12/07, Kelley Trombly-Freytag <[EMAIL PROTECTED]> wrote:
Scott Battaglia <[EMAIL PROTECTED]> writes: > > > Have you configured your CAS url on the client to be https://[machine]:[port]/cas/login or https://[machine]:[port]/cas/ ? It should have a /login-Scott > If what you mean by "configuring my CAS url on the client" to be changing the cas-client.properties file as given in the example athttp://www.ja- sig.org/products/cas/client/client-java/index.html, I did not have it configured with the /login at the end - the example does not have it. When I add the /login at the end of the cas.server.url property, nothing different happens. We do not get redirected, we see the same successful login page. Could you give a pointer to a more recent set of configuration file examples than are at the URL above? Kelley _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
