ja-sig Java Client - setup problems, not redirecting after authentication

Scott Battaglia scott.battaglia at gmail.com
Fri Feb 9 14:44:38 EST 2007


Kelley,

You've most likely modified the CAS server's casLoginView.jsp and specified
an action in the form view that does not include the service parameter.

-Scott

On 2/9/07, Kelley Trombly-Freytag <kfreytag at fnal.gov> wrote:
>
> Our problem is that after the setup described below, we go to the
> casLoginGenericSuccess view instead of back to our application.
>
> I have recently downloaded CAS Server 3.0.6 Final and the JA-SIG CAS Java
> Client
> 3.0.
>
> We have verified that the CAS server installation on tomcat 5.0.30 works
> out of
> the box.
>
> We have created a mindless web application (that works). We then put the
> filter definitions per the current "JA-SIG CAS Client for Java", page;
> created
> the WEB-INF/securityConfiguration.xml and WEB-INF/cas-client.propertiesfiles.
>
> These were customized as follows:
> server.xml - we changed the CAS Validation Filter to be /*
> securityConfiguration.xm:
>        -for ticketValidator we got startup errors stating it could not
> find
>         a constructor to match our arguements (tomcat log). In checking
> out
>         the source, we noted there were 6 arguments in the example from
> the
>         web page, and either 5 or 8 in the most recent version of the
> source.
>         We went with the 5 argument constructor: using the properties for
>         casServerUrl and renew, leaving the example along for HttpClient,
>         proxyChains (which was null) and acceptAnyProxy (true).
>
>        -for the casValidationFilter argument #1, we gave the
>        URL of our application as follows serverName:8080/castest
>
>        -for the casAuthenticationFilter argument #1, we gave the same URL
>        as for casValidationFilter
> cas-client.properties:
>        -we changed all references to localhost:8443 to serverName:8443
>
> Invoking our web application correctly sends us to CAS to authenticate,
> which
> we do. Then, as stated above, we get the casLoginGenericSuccess view,
> instead of
> being redirected.
>
> Can someone give us advice on what we are doing wrong?
>
> Kelley Trombly-Freytag
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20070209/b2551cf7/attachment.html 


More information about the cas mailing list