CAS Problem - OtagoPolytechnic/opp-user GitHub Wiki

###The Problem with the CAS version 3.5.2

The problem with the CAS version 3.5.2 was couldn’t access the CAS web management page. The web management page is very important for when you are trying assign CAS as single-sign-on with other web application and also to setup the other feature for CAS. The error that CAS had give out was an error 500 connection time out. For this we did a lot of research around the internet to find the solution for this but there was no solution that could fix this problem at all. I asked Christopher to help me out to find the solution for this as he have been working with the deployment of the JAVA environment before and he still have no answer for this solution. At the end I had made a suggestion to Adon, we need someone that had an experience with CAS before to help us out. Adon had email one of the staff at the University who Adon have been working with before. We had meet up with Richard Zinn who work at University and who has been working with CAS before. He had a look at the CAS and tried a lot of the things that could be a solution for this but in the end we still couldn’t solve the problem. He had a suggestion on couple of things that we could do a research on and that could lead to the solution to solve this problem. He also going to give us the configuration to compare it with the CAS that he had setup and I think that also could be the answer for this problem.

The idea for the solution of this problem

• Ask Adon for the Configuration file from Richard and compare them with the one that is on the CAS server
• Use the letsencrypt to setup the SSL/TLS Certificate for the Tomcat