Deprecation Notice (25 February 2011):
The Soulwing CAS client is officially deprecated. I will continue to provide minimal support for it for existing users. Those interested in CAS integration for Confluence, Jira, and Tomcat are strongly encouraged to use the official Jasig CAS client. The official client supports all of the functionality provided by the Soulwing CAS client, and many new features -- support for SAML, single sign-out, etc...
Container-Managed CAS Documentation updated for Tomcat 6 (10 March 2009):
The documentation for configuring container-managed CAS in Tomcat has been updated for Tomcat 6. The configuration has been tested with version 0.5.3 of the client running in Tomcat 6 on Linux, Mac OS X, and Windows.
Soulwing CAS Client is a client-side implementation of the Central Authentication Service protocol suitable for use in Java-based web applications. The central aim of this project is to provide a CAS client component that can be easily integrated into traditional and off-the-shelf Java web applications as well as modern web applications based on dependency injection frameworks such as Spring.
Main features and benefits:
- Full support for the CAS 2 authentication protocol
- Servlet filters for CAS serviceValidate and proxyValidate authentication
- Proxy ticket service components for providing CAS authentication tickets to backend applications/services
- Simplified CAS protocol configuration for ease of application deployment
- All components and servlet filters configurable as beans in a
dependency injection (IoC) framework (e.g.
or via traditional
The flexible configuration of Soulwing CAS Client makes it highly suitable for adding CAS authentication to off-the-shelf applications. The package includes Seraph authenticators for Atlassian Confluence and JIRA along with instructions for CAS enabling these great applications.