Apereo CAS - Enterprise Single Sign On for all
Java CSS HTML JavaScript Other
Latest commit 488e305 Sep 27, 2016 @mmoayyed mmoayyed updated docs

README.md

Central Authentication Service (CAS)

License Maven Central Github Releases Stack Overflow Dependency Status JavaDoc Codacy Badge CLA assistant

Introduction

Welcome to the home of the Central Authentication Service project, more commonly referred to as CAS. CAS provides enterprise single sign-on for the web and attempts to be a comprehensive platform for your authentication and authorization needs.

CAS provides an extensive list of features for most application requirements and integrations, offers community documentation and implementation support, has an extensive community of adopters and is virtually supported by most programming languages, frameworks and products.

CAS is an open and well-documented authentication protocol. The primary implementation of the protocol is an open-source Java server component by the same name, hosted here.

Features

The following features are supported by the CAS project:

  • CAS v1, v2 and v3 Protocol
  • SAML v1 and v2 Protocol
  • OAuth Protocol
  • OpenID & OpenID Connect Protocol
  • Authentication via JAAS, LDAP, RDBMS, X.509, Radius, SPNEGO, JWT, Stormpath, Remote, Trusted, BASIC, Apache Shiro, MongoDb, Pac4J and more.
  • Delegated authentication to WS-FED, Facebook, Twitter, SAML IdP, OpenID, OpenID Connect, CAS and more.
  • Authorization via ABAC, Time/Date, Internet2's Grouper and more.
  • HA clustered deployments via Hazelcast, Ehcache, JPA, Memcached, Apache Ignite, Couchbase and more.
  • Application registration backed by JSON, LDAP, JPA, Couchbase, MongoDb and more.
  • Multifactor authentication via Duo Security, YubiKey, RSA, Google Authenticator and more.
  • Administrative UIs to manage logging, monitoring, statistics, configuration, client registration and more.
  • Global and per-application user interface theme and branding.

The foundations of CAS are built upon: Spring Framework, Spring Boot, Spring Cloud, Spring Session and Thymeleaf.

Documentation Gitter

Deployment Build Status Issue Stats Issue Stats

It is recommended to build and deploy CAS locally using the WAR Overlay method. This approach does not require the adopter to explicitly download any version of CAS, but rather utilizes the overlay mechanism to combine CAS original artifacts and local customizations to further ease future upgrades and maintenance.

Note: Do NOT clone or download the CAS codebase directly. That is ONLY required if you wish to contribute to the development of the project. Utilize the WAR Overlay method instead to build and deploy your CAS instance.

Contributions