Some JAAS frameworks (e.g. JBoss 5) may create an implicit principal from username/password credentials passed into the JAAS pipeline. Since the CAS service URL is used for the username part of the credential, support has been added to append a unique suffix to the service URL and make it available to the custom AssertionPrincpal princpal type. A unqiue URL is generated prior to invoking WebAuthentication#login() to account for this feature of JBoss 5. |
||
|---|---|---|
| cas-client-core | ||
| cas-client-integration-atlassian | ||
| cas-client-integration-jboss | ||
| cas-client-integration-tomcat-common | ||
| cas-client-integration-tomcat-v6 | ||
| cas-client-integration-tomcat-v7 | ||
| cas-client-support-distributed-ehcache | ||
| cas-client-support-distributed-memcached | ||
| src/licensing | ||
| .gitignore | ||
| LICENSE | ||
| README.txt | ||
| assembly.xml | ||
| pom.xml | ||
README.txt
BUILDING THE CAS CLIENT FOR JAVA Please note that to be deployed in Maven Central, we mark a number of JARs as provided (related to JBoss and Memcache Clients). In order to build the clients, you must enable the commented out repositories in the appropriate pom.xml files in the modules (cas-client-integration-jboss and cas-client-support-distributed-memcached) or follow the instructions on how to install the file manually.