Hi,
I don't see anything in my application log, the only log entry I see
is in my access log. Seeing you mention SAML in your post, makes me
think that maybe I'm not using the correct filters.
This is my current filter setup in my client Java app:
<filter>
<filter-name>CASSingleSignOutFilter</filter-name>
<filter-class>
org.jasig.cas.client.session.SingleSignOutFilter
</filter-class>
<init-param>
<param-name>artifactParameterName</param-name>
<param-value>ticket</param-value>
</init-param>
</filter>
<filter>
<filter-name>CASAuthenticationFilter</filter-name>
<filter-class>
org.jasig.cas.client.authentication.AuthenticationFilter
</filter-class>
<init-param>
<param-name>casServerLoginUrl</param-name>
<param-value>
https://quicksilver-vm2:8443/cas/login
</param-value>
</init-param>
<init-param>
<param-name>service</param-name>
<param-value>
http://17inchVista:8180/CRISCAS/pages/index.jsf
</param-value>
</init-param>
<init-param>
<param-name>serverName</param-name>
<param-value>http://17inchVista:8180</param-value>
</init-param>
<init-param>
<param-name>renew</param-name>
<param-value>false</param-value>
</init-param>
<init-param>
<param-name>gateway</param-name>
<param-value>false</param-value>
</init-param>
<init-param>
<param-name>artifactParameterName</param-name>
<param-value>ticket</param-value>
</init-param>
<init-param>
<param-name>serviceParameterName</param-name>
<param-value>service</param-value>
</init-param>
<init-param>
<param-name>encodeServiceUrl</param-name>
<param-value>true</param-value>
</init-param>
</filter>
<filter>
<filter-name>CASValidationFilter</filter-name>
<filter-class>
org.jasig.cas.client.validation.Cas20ProxyReceivingTicketValidationFilter
</filter-class>
<init-param>
<param-name>casServerUrlPrefix</param-name>
<param-value>https://quicksilver-vm2:8443/cas</param-value>
</init-param>
<init-param>
<param-name>serverName</param-name>
<param-value>http://17inchVista:8180</param-value>
</init-param>
</filter>
<filter>
<filter-name>CASHttpServletRequestWrapperFilter</filter-name>
<filter-class>
org.jasig.cas.client.util.HttpServletRequestWrapperFilter
</filter-class>
</filter>
<filter>
<filter-name>CASAssertionThreadLocalFilter</filter-name>
<filter-class>
org.jasig.cas.client.util.AssertionThreadLocalFilter
</filter-class>
</filter>
Is this okay?
2009/5/5 Marvin Addison <[email protected]>:
> In addition to the filter configuration, you need the following in
> your application web.xml:
>
> <listener>
> <listener-class>
> org.jasig.cas.client.session.SingleSignOutHttpSessionListener
> </listener-class>
> </listener>
>
> Much more valuable than the access log is your application log. The
> org.jasig.cas category will emit a DEBUG message like the following if
> it correctly receives the SAML logout assertion sent by the server:
>
> 2009-01-07 16:16:20,229 DEBUG
> [org.jasig.cas.client.session.SingleSignOutHttpSessionListener]
> Removing HttpSession: sPt6tRJloLpInuAg7o0lWg**
>
> Hope that helps,
> M
>
> --
> 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
>
--
Venka Ashtakala, B.Eng, G.C. Eng
Venka Ashtakala & Associates
Software Development Consultants
Office: +1-703-596-0287
Fax: +1-815-550-1356
Mobile: +91 9886304317
[email protected]
--
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
