Package org.jasig.cas.web

In the Servlet API, the WEB-INF/web.xml deployment descriptor maps various URL values to Java classes.

See: Description

Class Summary

Class	Description
DelegateController	Abtsract class to be extended by all controllers that may become a delegate.
DelegatingController	Delegating controller.
HealthCheckController	Reports overall CAS health based on the observations of the configured HealthCheckMonitor instance.
LogoutController	Controller to delete ticket granting ticket cookie in order to log out of single sign on.
NoSuchFlowExecutionExceptionResolver	The NoSuchFlowExecutionResolver catches the NoSuchFlowExecutionException thrown by Spring Webflow when the given flow id no longer exists.
OpenIdProviderController	Maps requests for usernames to a page that displays the Login URL for an OpenId Identity Provider.
ProxyController	The ProxyController is involved with returning a Proxy Ticket (in CAS 2 terms) to the calling application.
ServiceValidateController	Process the /validate and /serviceValidate URL requests.
StatisticsController

Package org.jasig.cas.web Description

In the Servlet API, the WEB-INF/web.xml deployment descriptor maps various URL values to Java classes. In Spring, the web.xml maps all URL program requests to a single generic handler. The mapping of particular URL values to particular classes is then part of the Spring configuration, specifically in the cas-servlet.xml file:

<!-- Handler Mapping -->
<bean id="handlerMapping" class="org.springframework.web.servlet.handler.SimpleUrlHandlerMapping">
 <property name="mappings">
  <props>
   <prop key="/login">loginController</prop>
   <prop key="/logout">logoutController</prop>
   <prop key="/serviceValidate">serviceValidateController</prop>
   <prop key="/validate">legacyValidateController</prop>
   <prop key="/proxy">proxyController</prop>
   <prop key="/proxyValidate">proxyValidateController</prop>
   <prop key="/CentralAuthenticationService">xFireCentralAuthenticationService</prop>
 </props>
</bean>

Each named service is then configured as a bean. For example, the /login processing is defined as

<bean id="loginController" class="org.jasig.cas.web.LoginController" autowire="byType">
<property name="loginTokens" ref="loginTokens" />
<property name="centralAuthenticationService" ref="centralAuthenticationService" />
</bean>

This package then supplies the classes that implement each of the URL services that are defined as part of the HTTP CAS protocol. Each such class is what Spring calls a Controller (from the MVC or Model, View, Controller paradigm). Generically, Controllers extract information from the HttpRequest object (Cookies, Headers, Certificates, Query parameters, etc.). In CAS, each Controller then calls the CAS layer to perform some operation involving tickets. The successful return object or failure from CAS is then added to a Map called the Model and is passed to a JSP page or Java class called the View that writes back a response.