The client sends the return url to the CAS Server. The CAS Server then uses that url to determine which service is calling it. If you look at the URL when the user is redirected to the CAS Server the Query String has a service= parameter.
> > > >Subject: Re: CAS 101 >From: [email protected] >Date: Wed, 27 Mar 2013 19:52:06 +0900 (JST) >X-Message-Number: 2 > >Looks like I had made some mistakes in importing certificate(s) of the >CAS server. >I got it working, but I am still at dark which piece of config (or code) >is responsible for redirection. > >--- On Wed, 2013/3/27, [email protected] <[email protected]> wrote: > >Hi all, >How does CAS know where to direct to after successful authentication? >I am asking because I am seeing "failed to properly redirect" error in >Firefox. > >Taking a simple example, say, I type https://test.server/helloworld. >Since I have my filters in the web.xml file (of that "helloworld" webapp) >in place, I am taken to CAS login page, and I enter my user and password, >and instead of showing me helloworld application (which just prints >"hello world" in the screen), I am greeted with redirection failure. > >Tomcat's catalina.out does not show any error, so CAS itself is properly >configured, I think. Where do I configure the "go here after >authentication" part? > >Some pointers would be helpful. > >Thanks. > > > > -- 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
