I have a .NET client that uses CAS single sign on. When I hit CAS 3.x setup by someone else, I redirect to CAS, authenticate to CAS and then redirect back to my site.
I setup a CAS 4 server on my local machine to test in development. In Windows, I installed tomcat 8.0.14 (the latest). I then auto-deployed CAS mostly out-of-the box no changes made from the original I can navigate directly to the site and login using the default "casuser / Mellon" credentials. (note that my machine name is pitonyakvm-02 and everything is running locally for this test). https://pitonyakvm-02:8443<https://pitonyakvm-02:8443/>/cas-server-webapp-4.0.0/login<http://localhost:8080/cas-server-webapp-4.0.0/login> When I use my client to login, it properly redirects to CAS, CAS shows the login page, I use the default credentials, I am then told that I authenticated but I do not redirect back to my client. Did I miss a simple property that tells CAS to redirect back after login rather than simply showing the screen that tells me that I successfully authenticated? I assume that my client is sending the correct things since I am able to hit the 3.x version, login, and redirect back correctly. In this case, CAS is external to my machine. My first thought is that I need to change something in the login-webflow.xml, but I thought that it was configured by default to redirect. Is it possible that tomcat deploys by default to not allow redirections? [cid:[email protected]] Andrew D. Pitonyak Principal Research Scientist Health & Analytics 505 King Avenue, Columbus, OH 43201 P: 614-424-5252 -- 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
