Are your clients protected with the Java client? If so, make sure the filters are ordered correctly (if they are in the wrong order, the auth. request can kick off before the sign out request).
On Tue, Jul 6, 2010 at 2:41 PM, Bryan Wooten <[email protected]> wrote: > So after much debugging I have come to the conclusion that there is some > wrong with both Sun App servers (our proxy) and Glassfish. > > > > I wrote a simple test application using HttpClient that does a post to my > CASified application with a fake logout request. All I get back are 301s or > 302s. I get the 302s when the 2 apps are on the glassfish instance and the > 301s when the CASified app is behind our proxy. > > > > What is weird is that we use HttpClient to POST to our PeopleSoft Weblogic > servers successfully. Also we have many apps that do forms posts (JSF pages) > that successfully make it through the proxy. > > > > I am at a loss to explain this behavior. Not having much luck with google, > so I guess I’ll have to post a question on the glassfish forums. > > > > Thanks everyone for your help. > > > > Bryan Wooten > > > > [email protected] > > Work: 801.585.9323 > > Cell: 801.414.3593 > > > > -- > 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 > > -- 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
