Hello, I've been trying to CASify Oracle Beehive with very little luck. I have to admit that I am fairly new to CAS (and Beehive) so it could be that I am doing something wrong. Anyway, this is what I've done so far (I am eliminating some Oracle Specific steps to concentrate on the CAS piece):
* Copied cas-client-core-3.2.0.jar and commons-logging-1.1.jar into WEB-INF/lib * Modified web.xml to add the filters as per https://wiki.jasig.org/display/CASC/Configuring+the+JA-SIG+CAS+Client+for+Java+in+the+web.xml * Modified a piece of code (Beehive PAM plugin) to get the username from the request as o request.getRemoteUser(); The problem is that when I bounce the application, it fails to start. If I remove my changes to web.xml (remove the filters) the application starts just fine so I am not sure if I am missing a .jar file or something. These are the filters I am trying to add: <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://login.server.com/cas/login</param-value> </init-param> <init-param> <param-name>serverName</param-name> <param-value>https://beehive.server.com</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://login.server.com/cas</param-value> </init-param> <init-param> <param-name>serverName</param-name> <param-value>https://beehive.server.com</param-value> </init-param> <init-param> <param-name>proxyCallbackUrl</param-name> <param-value>https://beehive.server.com/proxyCallback</param-value> </init-param> <init-param> <param-name>proxyReceptorUrl</param-name> <param-value>/proxyCallback</param-value> </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-mapping> <filter-name>CAS Authentication Filter</filter-name> <url-pattern>/teamcollab/*</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>CAS Validation Filter</filter-name> <url-pattern>/proxyCallback</url-pattern> </filter-mapping> Do you guys have any advice? I saw an e-mail from Scott a few weeks ago in which he pointed out that it was possible to just "re-create" the CAS filters ..."You'll essentially need to re-create what the CAS filters do (which is essentially detect whether you're (a) already logged in or (b) presenting a ticket and then validate the ticket or redirect)...." Thanks, ~Alex -- 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
