For example CAS 2 used its own custom login token whereas we handle the same situation by using Webflow in CAS 3 (which is why there are additional parameters).
I'd recommend following the example/demo JSP pages. They should be a good indication of what is required on the page.
-Scott
On 9/4/06, Velpi <[EMAIL PROTECTED]> wrote:
> can someone please correct the docu on the following protocoll page:
> http://www.ja-sig.org/products/cas/overview/protocol/index.html
>
> section 2.1.3 says the form must include lt, username and password.
> But it must also include _eventId=submit - otherwise it seems not to work.
Although it would be nice to have this documented somewhere, that is not the
right spot. The document you are referring to is the general CAS *protocol*
specification. This means that a decent CAS implementation should comply with
that specification (and not the other way around). It's not the JA-SIG CAS3
implementation specification and thus does not reflect its internals.
Feel free to make a list of things you found that are missing in the
documentation so it can be added to the documentation somewhere.
-- Velpi
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
