The server logs clearly show that authentication succeeded, and there
are no obvious signs in the client logs of client-server
communications problems.  (SSL problems are the most common cause of
problems.)  That leaves the following:

SEVERE: java.io.IOException: Server returned HTTP response code: 503
for URL: http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd
java.io.IOException: Server returned HTTP response code: 503 for URL:
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd

That appears to be an error thrown by the Xerces XML parser when it
attempts to load a DTD for validating the XML response.  I can
manually GET that resource from a browser (i.e. no 503 error), but
that doesn't really address _why_ the parser is trying to load an
_HTML_ DTD for the CAS service validation response which is XML.  I
suspect a servlet configuration problem where the /serviceValidate URI
is returning HTML instead of CAS XML.

M

-- 
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

Reply via email to