Logging out of CAS merely ends CAS's Single Sign On session. It has no
effect on any sessions currently established in any other application.
-Scott
On 5/27/07, Makan <[EMAIL PROTECTED]> wrote:
I've deployed CAS server on tomcat and liferay ( using liferay cas-web
and default configuration specified in the liferay cas integration manual
)
and every thing was going on till I decided to apply the same filter on
another web application on the same server,
the point is here than when I logged in through any of these
applications I will be logge in into others but when I logged out with:
final String CAS_FILTER_USER =
"edu.yale.its.tp.cas.client.filter.user";
final String CAS_FILTER_RECEIPT =
"edu.yale.its.tp.cas.client.filter.receipt";
final String LOGOUT_URL = "https://localhost:8443/cas-web/logout";;
...
session.removeAttribute(CAS_FILTER_USER);
session.removeAttribute(CAS_FILTER_RECEIPT);
session.invalidate();
response.sendRedirect(LOGOUT_URL);
knowing that the logout was successfull ( be cause when trying to login
into any applications I will be redirected to the login screen ), if I
have any openning browser window ( think of two simultanous
web-applications running on the same server and logging out from one of
them ), I can resume working with another one!
don't know what exactly the problem is, tried to use "Extended Java
Client" which gives me a JNDI Server-based ( not default yale client
applications-based) configuration but nothing changed.
moving a while in forums and nothing found , but looking at CASFilter
source code, found that trying to remove attribute from one session , do
not help the filter to block the running of other one, dont know what to
do else!
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
--
-Scott Battaglia
LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
