We recently upgraded one of our Application Servers which formerly worked perfectly together with our CAS Server. Now, after we upgraded that Tomcat Server it's impossible to Log into the Webapp on this Server using CAS anymore. The Login Form from the CAS Server still appaers, but after entering the credentials and submitting the Form there's only a blank, white screen.
CAS itself still works fine with other Applications and Servers in our Network.
When I log in to the Webapp on the upgraded Server, I see from the CAS Servers Logs that these steps are successfull:
ACTION: AUTHENTICATION_SUCCESS
...
ACTION: TICKET_GRANTING_TICKET_CREATED
...
ACTION: SERVICE_TICKET_CREATED
...
But there is no more Message about Ticket Validation in the Logs of the CAS Server.
In the Logs of the App server on the other Hand I can see this:
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1624)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
at org.jasig.cas.client.util.CommonUtils.getResponseFromServer(CommonUtils.java:281)
at org.jasig.cas.client.validation.AbstractCasProtocolUrlBasedTicketValidator.retrieveResponseFromServer(AbstractCasProtocolUrlBasedTicketValidator.java:33)
at org.jasig.cas.client.validation.AbstractUrlBasedTicketValidator.validate(AbstractUrlBasedTicketValidator.java:178)
at com.liferay.portal.servlet.filters.sso.cas.CASFilter.processFilter(CASFilter.java:194)
at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:59)
I can't imagine were a FileNotFoundException may come from in the context of Validating a CAS Ticket. Any hints about what may cause this Error and prevents me to Log in to my Web App with CAS?