On Fri, 25 Mar 2011, Laura Griffel wrote:
Hi all,
I have several client applications that I'm CASifying. I have my cas
server up and running fine, and put I followed the instructions to
CASify two java client applications. The authentication part works, and
getting the ldap attributes works too. My problem is that the single
sign on part does not work.
If I go to the first application, it redirects me to CAS and logs me in
fine. If I click on a link inside the first application to the second
application, the second application's Authentication filter says 'no
ticket and no assertion found' and redirects me back to the CAS login to
login again. Obviously, since the second application is protected by
CAS, I don't want to have to login again. Is there something special I
need to turn on to handle this?
That is the correct behavior. The CAS server checks for the CASTGC (CAS
Ticket Granting Cookie) when the browser returns to CAS. If the CASTGC is
valid, CAS will generate a new Service Ticket and redirect back to the
second application.
When the CASTGC is present and all the pieces are working properly, you
don't see the CAS page in your browser, even though the second application
bounced you through CAS.
Andy
--
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
