I did change the order also. However, I understood later that the validation filter was not even called. This is the contrary of what I had mentioned in my initial post.
I ended up changing the casServiceValdationSuccess.jsp to include user attributes and reverting back to CAS protocol and not SAML. Also I changed the deployerConfigContext.xml in server and used org.jasig.services.persondir.support.jdbc.MultiRowJdbcPersonAttributeDao to get the multiple rows result for a logged in user. It would be nice to get SAM to work however, for some reason I am not able to get it to work. Regards, Raj (Vasanth Tatta) Principal J2EE Engineer Beachbody.com On 2/4/13 6:33 AM, "Marvin Addison" <[email protected]> wrote: >> <filter-mapping> >> <filter-name>CAS Validation Filter</filter-name> >> <url-pattern>/*</url-pattern> >> </filter-mapping> >> >> <filter-mapping> >> <filter-name>CAS Authentication 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> > >The order of filter-mapping elements determines filter execution >order. I noted that your filters are not ordered as recommended on the >wiki [1]. You might also try adding the AssertionThreadLocalFilter to >the chain to see whther that helps. > >M > >[1] >https://wiki.jasig.org/display/CASC/Configuring+the+Jasig+CAS+Client+for+J >ava+in+the+web.xml > >-- >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
