[cas-dev] Migrating hacking CAS 2 behavior to login-webflow?

[Patrick Berry]

We have single sign-on to PeopleSoft.  It's a total hack with a Java client
and it's being replaced with a PeopleCode client (that we will share when we
can).  But...until such time I need to support the existing client.  Now, I
know that PeopleSoft will not accept auth via GET, only POST.  We are
running CAS 2 and we get it to work like so...

In the web.xml for CAS 2 we have this:
<!-- Page URL for login success message when 'service' is specified -->
 <context-param>
        <param-name>edu.yale.its.tp.cas.serviceSuccess</param-name>
        <param-value>/goService.jsp</param-value>
    </context-param>

Then in goService.jsp we have this:
  if ((serviceId.indexOf("cmsweb.csuchico.edu") != -1) ||
(serviceId.indexOf("cmsdev.calstate.edu") != -1))
  {
    pageContext.forward("goServicePsft.jsp");

  }

Then in goServicePsft.jsp we something similar to the
casPostResponseView.jsp which submits the ticket from a form that
auto-submits on load.

Now, my question is should I be looking at the login-webflow.xml to get this
same behavior in CAS3?  I'm not entirely sure how to convince CAS that a
service needs to get the ticket via POST.

Thanks,
Pat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas-dev/attachments/20080707/06a35114/attachment.html