Session Storage

The CAS team understands that different deployers are going to have different deployment needs. For example, smaller organizations, with a less critical infrastructure, may only use one CAS server, and thus have a rather simple deployment. Larger organizations or universities may have more complex requirements including load balanced machines, load balanced machine rooms, etc. which may require that multiple CAS instances share the same set of data. Because of that, CAS offers multiple storage mechanisms for sessions.

As of the CAS4 release, the following mechanisms are supported:

• Memcached Session Storage
• JPA Session Storage
• In-Memory Session Storage