Sorry for taking your time. Actually due to problem in my log4j configuration, I had missed the error message for connection timeout while sending log out request. Actually the post request had failed duet to connection problem.
Lekhnath Bhusal wrote: > Hello team, > I am using CAS client 3.2.1 and CAS server 3.1.3 for authentication. > Previously single sign out worked well. Today, I could not log out > from any of my product. When I traced down the problem, I found that > filter expects POST method for logging out request and I am getting > all requests as GET. I could not figure out how the request converted > to GET, as logout request is sent through HTTP post from the logout > controller. > Please suggest me if there may be anything that abruptly converted the > request type. > Regards, > Lekhnath > PRIVACY NOTICE This email and any attachments may be confidential and/or privileged. Use of the information contained in this email by anyone other than the intended recipient is strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and delete this email. _______________________________________________ cas-dev mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas-dev
