First, have you carefully reviewed the instructions at https://wiki.jasig.org/display/CASC/JAAS+Integration?
> i used the CAS20TicketValidator because the SAML11 one is getting to a lot of > exceptions (especially at ReflectUtils I would be interested to know what exceptions you're getting. Could you post stack traces? > <login-module code="org.jasig.cas.client.jaas.CasLoginModule" flag="optional"> > > <module-option > name="ticketValidatorClass">org.jasig.cas.client.validation.Cas20ServiceTicketValidator</module-option> > <module-option > name="casServerUrlPrefix">http://localhost:9999/CASServer</module-option> > <module-option name="tolerance">20000</module-option> > <module-option > name="casLogin">http://localhost:9999/CASServer/login</module-option> > <module-option > name="casLogout">http://localhost:9999/CASServer/logout</module-option> > <module-option > name="casLogin">http://localhost:9999/CASServer/login</module-option> > <module-option > name="casValidatePrefix">http://localhost:9999/CASServer</module-option> > <module-option name="casServiceValidate">serviceValidate</module-option> > <module-option > name="casServerName">http://localhost:9999/CASServer</module-option> > > </login-module> You have some invalid parameters in the module options above. See https://wiki.jasig.org/display/CASC/JAAS+Integration for the complete listing of valid parameters, including required ones. > ive got it working with a similar configuration: Java Client 3.1.x + JBoss > Portal 2.7.2 + CAS 3.4.2.1, however i used the Valve to redirect directly to > the CAS Server The CASWebAuthenticationFilter servlet filter serves this purpose for the JAAS integration, although I suppose there are other ways this could be accomplished as you noted. But the use of servlet filters keeps with the traditional method of Java CAS client configuration. 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
