CAS Authentication
As of uPortal 3.2.0, uPortal uses the Jasig CAS client for CAS authentication. Previous versions of the portal used the older Yale CAS client. The filter configuration for the current Jasig client is somewhat different, so implementations using CAS would be well advised to look over the new default web.xml file while upgrading to uPortal 3.2.
Bundled CAS Server Upgrade
Between uPortal 3.1 and 3.2, the bundled CAS server was upgraded from CAS 3.3.1 to 3.3.5. As of CAS 3.3.5, the CAS project dropped some of its custom LDAP handling code in favor of improvements to the Spring LDAP project.
uPortal installations that use the bundled CAS server for LDAP authentication will need to switch from CAS's AuthenticatedLdapContextSource to the Spring-provided org.springframework.ldap.core.support.LdapContextSource. This change also involves modifying several of that bean's properties.
More details on configuring CAS for LDAP authentication can be found in the CAS wiki.