My filter setup looks like this:
<!-- FILTERS -->
<filter>
<filter-name>CAS Single Sign Out Filter</filter-name>
<filter-class>org.jasig.cas.client.session.SingleSignOutFilter</
filter-class>
</filter>
<filter>
<filter-name>CAS Authentication Filter</filter-name>
<filter-
class>org.jasig.cas.client.authentication.AuthenticationFilter</filter-
class>
<init-param>
<param-name>casServerLoginUrl</param-name>
<param-value>https://auriga:8443/cas/login</param-value>
</init-param>
<init-param>
<param-name>serverName</param-name>
<param-value>http://auriga:8080</param-value>
</init-param>
<init-param>
<param-name>service</param-name>
<param-value>http://auriga:8080/aquila</param-value>
</init-param>
</filter>
<filter>
<filter-name>CAS Validation Filter</filter-name>
<filter-class>
org
.jasig
.cas.client.validation.Cas20ProxyReceivingTicketValidationFilter</
filter-class>
<init-param>
<param-name>casServerUrlPrefix</param-name>
<param-value>https://auriga:8443/cas/</param-value>
</init-param>
<init-param>
<param-name>service</param-name>
<param-value>http://auriga:8080/aquila</param-value>
</init-param>
<init-param>
<param-name>redirectAfterValidation</param-name>
<param-value>true</param-value>
</init-param>
</filter>
<filter>
<filter-name>CAS HttpServletRequest Wrapper Filter</filter-name>
<filter-class>
org.jasig.cas.client.util.HttpServletRequestWrapperFilter</filter-
class>
</filter>
<filter>
<filter-name>CAS Assertion Thread Local Filter</filter-name>
<filter-class>org.jasig.cas.client.util.AssertionThreadLocalFilter</
filter-class>
</filter>
<filter>
<filter-name>opensessioninview</filter-name>
<filter-class>
org.springframework.orm.hibernate3.support.OpenSessionInViewFilter
</filter-class>
</filter>
<filter>
<filter-name>WebApplication</filter-name>
<filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-
class>
<init-param>
<param-name>applicationFactoryClassName</param-name>
<param-value>org.apache.wicket.spring.SpringWebApplicationFactory</
param-value>
</init-param>
</filter>
<!-- FILTERS MAPPINGS -->
<filter-mapping>
<filter-name>CAS Single Sign Out Filter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>CAS Authentication Filter</filter-name>
<url-pattern>/app/account/*</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>CAS Authentication Filter</filter-name>
<url-pattern>/app/admin/*</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>CAS Validation Filter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>CAS HttpServletRequest Wrapper Filter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>CAS Assertion Thread Local Filter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>opensessioninview</filter-name>
<url-pattern>/app/*</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>WebApplication</filter-name>
<url-pattern>/app/*</url-pattern>
</filter-mapping>
<!-- LISTENERS -->
<listener>
<listener-
class>org.jasig.cas.client.session.SingleSignOutHttpSessionListener</
listener-class>
</listener>
<listener>
<listener-
class>org.springframework.web.context.ContextLoaderListener</listener-
class>
</listener>
Am 08.05.2009 um 02:42 schrieb Marvin Addison:
>> whenever the logout
>> is fired in CAS, obviously a request is sent to the service, which
>> simply
>> "redirects" this request back to CAS. So it looks like it's
>> treating the
>> logout-command just as a regular request. What could be the reason
>> for this
>> behaviour?
>
> This could happen if you do not have the SingleSignOutFilter defined
> before all other CAS filters.
>
> 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
--
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
