/ #Apache Shiro #SSO 

Integrating Apache Shiro with CAS Authentication via LDAP

In this post I want to share how to setup SSO with CAS and LDAP authentication, and then demonstrate how to integrate Apache Shiro with CAS in the web application.

An Example of An Individual LDAP Entry

The following entry which represented in LDIF would be used to login the CAS. In this case, the username will be the full email address (case-insensitive) and the password is the value of userPassword attribute.

dn: cn=John Doe,dc=example,dc=com
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgPerson
cn: John Doe
sn: Doe
mail: john@example.com
userPassword:: e21kNX1HaDNKSEpCekpjYVNjZDN3eVVTOGNnPT0=

Maven Overlay Installation

Here we use Maven WAR overlay project to arrange customizations such as authentication handlers and UI design. Thanks Unicon Labs for providing a great starting simple-cas4-overlay-template. Next, we setup the local environment with the following instructions to meet the minimum requirements, including JDK 1.7+, Apache Maven 3+ and Servlet container supporting Servlet 3+ spec (e.g. Apache Tomcat 7+).

sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java7-installer
sudo apt-get install tomcat7
sudo apt-get install maven
sudo apt-get install git

Next, we clone the repository via:

git clone https://github.com/UniconLabs/simple-cas4-overlay-template.git

Note that we need to configure files in etc such as log4j.xml and cas.properties to satisfy local CAS installation needs, and then copy the files to the default external file system location /etc/cas. Finally, we run the chown command to change the owner and owning group of files with appropriate privilege.

sudo chown tomcat7:adm -R /etc/cas

Executing mvn clean package and then deploy the target/cas.war to a servlet container.

Non-Secure Connection

You will have Non-secure Connection message indicates you MUST log in over HTTPS. We need to prepare the certificate keystore and edit the Tomcat configuration file to support SSL.

keytool -genkey -alias tomcat -keypass changeit -keyalg RSA
keytool -export -alias tomcat -keypass changeit -file server.crt
sudo keytool -import -file server.crt -keypass changeit -keystore $JAVA_HOME/jre/lib/security/cacerts

We remove the comment tags from around the original example SSL connector and add the keystorePass and keystoreFile configurations in /var/lib/tomcat7/conf/server.xml.

<!-- Define a SSL HTTP/1.1 Connector on port 8443
       This connector uses the JSSE configuration, when using APR, the
       connector should be using the OpenSSL style configuration
       described in the APR documentation -->
    <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
                maxThreads="150" scheme="https" secure="true"
                keystorePass="changeit" keystoreFile="/home/ubuntu/.keystore"
                clientAuth="false" sslProtocol="TLS" />

Remember to restart tomcat using sudo service tomcat7 restart and visit CAS over HTTPS, we can except that:

Enable SSL/TLS

Now we can login the CAS with the default username casuser and password Mellon which defined in deployerConfigContext.xml.

CAS Log In Successful

In order to enable the LDAP integration in CAS we include the following dependency in pom.xml,


Let LDAP authentication performed with an anonymous search with the following configuration in /home/ubuntu/cas-server-4.0.0/cas-server-webapp/src/main/webapp/WEB-INF/deployerConfigContext.xml.


<bean id="authenticationManager" class="org.jasig.cas.authentication.PolicyBasedAuthenticationManager">
            <entry key-ref="ldapAuthenticationHandler" value="#{null}"/>
            <entry key-ref="proxyAuthenticationHandler" value-ref="proxyPrincipalResolver" />
    <property name="authenticationPolicy">
        <bean class="org.jasig.cas.authentication.AnyAuthenticationPolicy" />
<bean id="ldapAuthenticationHandler"
    <property name="principalAttributeMap">
            <entry key="member" value="member" />
            <entry key="mail" value="mail" />
            <entry key="displayName" value="displayName" />

<bean id="authenticator" class="org.ldaptive.auth.Authenticator"
      c:handler-ref="authHandler" />

<bean id="dnResolver" class="org.ldaptive.auth.PooledSearchDnResolver"
      p:userFilter="${ldap.searchFilter}" />
<bean id="searchPooledLdapConnectionFactory"
      p:connectionPool-ref="searchConnectionPool" />

<bean id="searchConnectionPool" parent="abstractConnectionPool" />

<bean id="abstractConnectionPool" abstract="true"
      p:connectionFactory-ref="connectionFactory" />

<bean id="ldapPoolConfig" class="org.ldaptive.pool.PoolConfig"
      p:validatePeriod="${ldap.pool.validatePeriod}" />

<bean id="connectionFactory" class="org.ldaptive.DefaultConnectionFactory"
      p:connectionConfig-ref="connectionConfig" />

<bean id="connectionConfig" class="org.ldaptive.ConnectionConfig"
      p:useStartTLS="${ldap.useStartTLS}" />

<bean id="pruneStrategy" class="org.ldaptive.pool.IdlePruneStrategy"
      p:idleTime="${ldap.pool.idleTime}" />

<bean id="searchValidator" class="org.ldaptive.pool.SearchValidator" />

<bean id="authHandler" class="org.ldaptive.auth.PooledBindAuthenticationHandler"
      p:connectionFactory-ref="bindPooledLdapConnectionFactory" />

<bean id="bindPooledLdapConnectionFactory"
      p:connectionPool-ref="bindConnectionPool" />

<bean id="bindConnectionPool" parent="abstractConnectionPool" />


LDAP Properties Starter

Then we add the corresponding LDAP properties to the WEB-INF/cas.properties configuration file.


# CAS Logout Behavior
# WEB-INF/cas-servlet.xml
# Specify whether CAS should redirect to the specified service parameter on /logout requests


# General properties

# LDAP connection timeout in milliseconds

# Whether to use StartTLS (probably needed if not SSL connection)

# LDAP connection pool configuration

# Amount of time in milliseconds to block on pool exhausted condition
# before giving up.

# Frequency of connection validation in seconds
# Only applies if validatePeriodically=true

# Attempt to prune connections every N seconds

# Maximum amount of time an idle connection is allowed to be in
# pool before it is liable to be removed/destroyed

# Authentication

# Base DN of users to be authenticated

# Search filter used for configurations that require searching for DNs


Once an overlay project has been created, remember to deploy the target/cas.war again and restart the Tomcat.


Finally, we use an example to illustrate the whole process. I created a new Maven project from servlet3-maven-archetype named java-servlet3-shiro-cas-client-demo in github, the file structure as following:

├── java-servlet3-shiro-cas-client-demo.iml
├── pom.xml
└── src
    ├── main
    │   ├── java
    │   │   └── org
    │   │       └── example
    │   │           ├── HelloServlet.java
    │   │           ├── LogoutServlet.java
    │   │           └── ProtectedServlet.java
    │   ├── resources
    │   │   └── shiro.ini
    │   └── webapp
    │       ├── WEB-INF
    │       │   ├── logback.xml
    │       │   └── web.xml
    │       └── index.jsp
    └── test
        ├── java
        └── resources

First add the Apache Shiro dependencies in pom.xml to enable the CAS support. Then we create a shire.ini indicates the Shiro use CasRealm in authentication. The web.xml set the filter to handle login/logout requests sent directly by the CAS server. The protected resources ProtectedServlet.java can be reached after authentication, and then you can check the subject’s principal and roles.