Re: CAS Filtering

Ryan Shelley Tue, 31 Oct 2006 13:40:41 -0800

There's actually a root path before the "gapi" which is why I have /gapi/* in the filter.

Ryan Shelley

Lead Developer

ITR Web Development/Middleware

California State University, Northridge

818.677.4258

[EMAIL PROTECTED]

On Oct 31, 2006, at 11:59 AM, Scott Battaglia wrote:

is "gapi" (i.e. http://localhost/gapi/PAGE) the application context? If so then you don't need it and can just do "/*" as it matches after the context.

-Scott

On 10/31/06, Ryan Shelley <[EMAIL PROTECTED]> wrote:

I'm in the process of developing a new servlet and have been looking at CAS filters as an option for CAS-ifying the servlet. I've been taking some examples from other implementations that use CAS Filters, however, my configuration seems to be flawed. When I access a resource that should be filtered by CAS, nothing actually happens (except the loading of the servlet, unsecured). I've checked both my App's logs and CAS's logs, but both show no activity. So, it's more than likely that I don't have my filter configured properly.

For reference, I'm running CAS Server 3.0.4, CAS Client 2.1.1, Spring 2.0 (I'm not sure if this is interfering).

I've been fiddling around with the url-patterns, but to no avail. I've also tried putting the filter before and after the Spring listeners, both with the same result.

Web.xml:

<?xml version="1.0" encoding="UTF-8"?>

<web-app ...>

<filter>
<filter-name>CAS Filter</filter-name>
<filter-class>edu.yale.its.tp.cas.client.filter.CASValidateFilter</filter-class>
<init-param>
<param-name> edu.yale.its.tp.cas.client.filter.loginUrl</param-name>
<param-value>https://cas-dev.csun.edu/cas/login </param-value>
</init-param>
<init-param>
<param-name>edu.yale.its.tp.cas.client.filter.validateUrl</param-name>
<param-value> https://cas-dev.csun.edu/cas/serviceValidate</param-value>
</init-param>
<init-param>
<param-name>edu.yale.its.tp.cas.client.filter.serverName</param-name>
<param-value> halcyon.csun.edu:8443</param-value>
</init-param>
</filter>

<filter-mapping>
<filter-name>CAS Filter</filter-name>
<url-pattern>/gapi/*</url-pattern>
</filter-mapping>

<context-param>
<param-name>log4jConfigLocation</param-name>
<param-value>/WEB-INF/conf/log4j.xml</param-value>
</context-param>

<context-param>
<param-name>webAppRootKey</param-name>
<param-value>gapi.root</param-value>
</context-param>

<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>/WEB-INF/conf/applicationContext.xml</param-value>
</context-param>

<listener>
<listener-class>org.springframework .web.util.Log4jConfigListener</listener-class>
</listener>

<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener </listener-class>
</listener>

<session-config>
<session-timeout>
30
</session-timeout>
</session-config>

<servlet>
<servlet-name>gapi</servlet-name>
<servlet-class>org.springframework. web.servlet.DispatcherServlet</servlet-class>
<load-on-startup>1</load-on-startup>
<init-param>
<param-name>contextConfigLocation</param-name>
<param-value>/WEB-INF/conf/gapi-servlet.xml</param-value>
</init-param>
</servlet>

<servlet-mapping>
<servlet-name>gapi</servlet-name>
<url-pattern>/gapi/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>gapi</servlet-name>
<url-pattern>/gapi</url-pattern>
</servlet-mapping>

</web-app>

Does anything seem glaringly wrong in this implementation of the filter?

Ryan Shelley
Lead Developer
ITR Web Development/Middleware
California State University, Northridge

818.677.4258
[EMAIL PROTECTED]

_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

Re: CAS Filtering

Reply via email to