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

[Scott Battaglia]

Pat,

We actually support POST its just something that hasn't been documented yet
(Adam mentioned it to me once that it wasn't documented, and I said "yes,
you're right, I should go do that" and then promptly forgot).

You just need to pass method=POST as part of the login url. (if I recall
correctly).

-Scott


-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia

On Mon, Jul 7, 2008 at 1:52 PM, Patrick Berry <pberry at gmail.com> wrote:

> 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
>
> _______________________________________________
> cas-dev mailing list
> cas-dev at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas-dev/attachments/20080707/c2cf81e3/attachment.html