Hi again,
I have a couple of questions on Single Sign Off:

Here's my setup:
I have my CAS 3.3.2 server running on a Tomcat5.5 server, and it does
support SSL.
My Java app is running in JBoss and it has been CASiffied with
cas-client-core-3.1.5.

Here's my problem:
I try to login to my Java app and am redirected to the CAS login page,
I login and am sent back to my Java app, where I am authorized to use
my Java app - this is all working as it should.  When I click on the
CAS logout link ( using HTTPS ), the webpage tells me that I have been
logged out successfully.  And, when I check the access log in JBoss, I
see this entry:

192.168.1.81 - - [05/May/2009:21:06:25 +0530] "POST
/CRISCAS/pages/index.jsf HTTP/1.1" 302 -

which is correct.

What is weird is that I have been running my Java app in debugger
mode, and, I've set breakpoints in the SingleSignOutFilter.doFilter()
and in the AuthenticationFilter.doFilter() and neither of these
breakpoints fire.  The only way I know that the CAS server executed
the Single Sign Off callback is by seeing this entry in the access
log.  Also, why is it giving an HTTP status of 302?  My goal is to
ultimately extend the SingleSignOffFilter so that I can invalidate my
application's session.  However, since the SingleSignOffFilter doesn't
seem to be getting called, I'm stuck.

Any help/comments/suggestions would be greatly appreciated!
Thanks
Venka

-- 
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

Reply via email to