Depending on choice of configuration components, there may be additional requirements such as LDAP directory, database, and caching infrastructure. In most cases, however, requirements should be self evident to deployers who choose components with clear hardware and software dependencies. In any case where additional requirements are not obvious, the discussion of component configuration should mention system, software, hardware, and other requirements.
CAS at its heart is a Java-based web application. Prior to deployment, you will need Java
There is no officially supported servlet container for CAS, but Apache Tomcat is the most commonly used. Support for a particular servlet container depends on the expertise of community members.
See this guide for more info.
Maven or Gradle overlays are provided to allow for a straightforward and flexible deployment solution. While it admittedly requires a high up-front cost in learning, it reaps numerous benefits in the long run.
You DO NOT need to have Maven or Gradle installed prior to the installation. They are provided to you automatically.
Internet connectivity is generally required for the build phase of any Maven-based project, including the recommended WAR overlays used to install CAS. Maven resolves dependencies by searching online repositories containing artifacts (jar files in most cases) that are downloaded and installed locally. While it is possible to override this behavior by altering Maven configuration settings, it is considered advanced usage and not supported.
A common solution to overcoming lack of Internet connectivity on a CAS server is to build CAS on a dedicated build
host with internet connectivity. The
cas.war file produced by the build is subsequently copied to the CAS server