Invalidating session on logout

Clears the Lightweight Third Party Authentication (LTPA) / single sign-on (SSO) cookies b. Removes the user from the authentication cache Source of Information :

topic=/websphere.express.doc/info/exp/ae/xsec_Any pointers, why Websphere behaves in such way..? [email protected] I had the same exact problem and I solved it via sending /ibm_security_logout requests to each of the Web Applications via AJAX when the user wants to logoff.

Maybe there is some other way of getting the list of WARs by inspecting the or some JEE API call..

This is how the code looks in my logoff JSP: I had the same exact problem and I solved it via sending /ibm_security_logout requests to each of the Web Applications via AJAX when the user wants to logoff.

invalidating session on logout-7invalidating session on logout-29invalidating session on logout-46

As per info center, when request is submitted to ibm_security_logout , it peforms following operation: a.

I was lucky in that we have an XML file which needs to be updated with the context root (and some other info) of all the Web Apps that run in EAR.

So I could easily get the list of all WARs in the EAR.

Hi All, I have implemented FORM-Based authentication in our application.

We are having multiple war file and each war file is deployed individually that means all war file are not packaged in a single EAR package.

Leave a Reply