...
- JPA
- JBoss Infinispan
- Memcached
- Ehcache
Authorization
CAS approaches authorization from the perspective that authorization is the responsibility of individual services that authenticate to CAS. This design owes to the history of CAS having been developed in the Higher Education setting, which is typically highly decentralized and ill suited to agreement and enforcement of centralized authorization policy. CAS supports decentralized authorization via an attribute release mechanism where any number of stores may be configured to load and store attributes about principals upon authentication to CAS, and which are released to services when they authenticate to CAS. Attributes are interpreted by services as needed, commonly for authorization and personalization.
Product Comparison
...
Support
CAS is supported by a community of developers and users via a variety of means:
- Formal product documentation
- Real-time user support via the cas-user@lists.jasig.org mailing list
- Jasig conferences
It is important to note that mailing list inquiries typically have response times measured in minutes, with resolutions often occurring same day if not first response. The CAS community spans multiple industries and the globe; with that breadth it is very likely that an active community member has an answer or insight to the problem at hand.
In addition to community support, a number of Jasig partners offer paid support for CAS: