I added a JIRA issue to include some debugging messaging CAS 3.1:
http://www.ja-sig.org/issues/browse/CAS-478
Thanks
-Scott
On 3/13/07, Luke McLean <[EMAIL PROTECTED]> wrote:
Thanks Scott,
I implemented some debugging and found that the status code being returned
was 500 (Internal Server Error). The problem turned out to be that the
ProxyTicketReceptor servlet was within the url-pattern of the CASFilter in
the web.xml file. I guess that this was setting up a continuous loop. I
moved the webapp down a directory, changed the filter and now it is
working.
Blessings,
Luke.
Generally that handler only fails for one of three reasons:
1. Invalid/missing certificate/mismatched host name.
2. Bad status code returned. By default the following status codes are
okay:
HttpURLConnection.HTTP_OK, HttpURLConnection.HTTP_NOT_MODIFIED,
HttpURLConnection.HTTP_MOVED_TEMP,
HttpURLConnection.HTTP_MOVED_PERM
,
HttpURLConnection.HTTP_ACCEPTED
3. Insecure URL when its expecting a secure url.
-Scott
--
View this message in context:
http://www.nabble.com/HttpBasedServiceCredentialsAuthenticationHandler-Query-tf3366911.html#a9464544
Sent from the CAS Users mailing list archive at Nabble.com.
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
--
-Scott Battaglia
LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
