Hello,
I'm trying to figure out if I have stumbled onto a bug in CAS or have a
configuration error.
I have an Active Directory in which users are stored in multiple containers.
While a single BindLdapAuthenticationHandler with the searchBase configured
to my AD domain root suffices to verify passwords, I found that I had to
configure separate CredentialsToLDAPAttributePrincipalResolver and
LdapPersonAttributeDao pairs for each user container as one of these would
not locate any users if the searchBase/baseDN was set to the AD domain
root. I have attached the config for reference.
Configuring multiple CredentialsToLDAPAttributePrincipalResolver and
LdapPersonAttributeDao pairs for each user container works fine for users in
the container listed first, but for users in the container listed second a
NullPointerException gets thrown in
cas-server-core/src/main/java/org/jasig/cas/authentication/principal/AbstractPersonDirectoryCredentialsToPrincipalResolver.java(Line
55)
35 public final Principal resolvePrincipal(final Credentials credentials) {
36 if (log.isDebugEnabled()) {
37 log.debug("Attempting to resolve a principal...");
38 }
39
40 final String principalId = extractPrincipalId(credentials);
41
42 if (principalId == null) {
43 return null;
44 }
45
46 if (log.isDebugEnabled()) {
47 log.debug("Creating SimplePrincipal for ["
48 + principalId + "]");
49 }
50
51 final Map<String, List<Object>> attributes =
this.attributeRepository.getMultivaluedUserAttributes(principalId);
52
53 final Map<String, Object> convertedAttributes = new
HashMap<String, Object>();
54
55 for (final Map.Entry<String, List<Object>> entry :
attributes.entrySet()) {
56 final String key = entry.getKey();
57 final Object value = entry.getValue().size() == 1 ?
entry.getValue().get(0) : entry.getValue();
58 convertedAttributes.put(key, value);
59 }
60 return new SimplePrincipal(principalId, convertedAttributes);
61 }
I'm guessing that this exception is being thrown because attributes is NULL
rather than an empty Map, but I don't know enough about Java maps or lists
to figure out in more detail the actual root cause. As well, I can't find
the source for
org.jasig.services.persondir.support.ldap.LdapPersonAttributeDao in the CAS
source to debug further.
If I try swapping the order of the CredentialsToPrincipalResolvers in my
config I find that both work when they are the first resolver. It seems that
if a user would be matched under the second container, the
NullPointerException occurs when the first
CredentialsToLDAPAttributePrincipalResolver is tried and CAS never gets to
the second resolver.
As a work-around I found that if I add a try/catch block around line 55 in
the AbstractPersonDirectoryCredentialsToPrincipalResolver I can get past the
NullPointerException and have success with the second resolver. This seems
like a kludge however.
So, can anyone tell me if I have a configuration problem or is this a bug in
CAS?
Thanks for any help,
Adam
--
Adam Franco
Middlebury College
[email protected]
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user<?xml version="1.0" encoding="UTF-8"?>
<!--
| deployerConfigContext.xml centralizes into one file some of the declarative configuration that
| all CAS deployers will need to modify.
|
| This file declares some of the Spring-managed JavaBeans that make up a CAS deployment.
| The beans declared in this file are instantiated at context initialization time by the Spring
| ContextLoaderListener declared in web.xml. It finds this file because this
| file is among those declared in the context parameter "contextConfigLocation".
|
| By far the most common change you will need to make in this file is to change the last bean
| declaration to replace the default SimpleTestUsernamePasswordAuthenticationHandler with
| one implementing your approach for authenticating usernames and passwords.
+-->
<beans xmlns="http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:tx="http://www.springframework.org/schema/tx";
xmlns:p="http://www.springframework.org/schema/p";
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.0.xsd";>
<!--
| This bean declares our AuthenticationManager. The CentralAuthenticationService service bean
| declared in applicationContext.xml picks up this AuthenticationManager by reference to its id,
| "authenticationManager". Most deployers will be able to use the default AuthenticationManager
| implementation and so do not need to change the class of this bean. We include the whole
| AuthenticationManager here in the userConfigContext.xml so that you can see the things you will
| need to change in context.
+-->
<bean id="authenticationManager"
class="org.jasig.cas.authentication.AuthenticationManagerImpl">
<!--
| This is the List of CredentialToPrincipalResolvers that identify what Principal is trying to authenticate.
| The AuthenticationManagerImpl considers them in order, finding a CredentialToPrincipalResolver which
| supports the presented credentials.
|
| AuthenticationManagerImpl uses these resolvers for two purposes. First, it uses them to identify the Principal
| attempting to authenticate to CAS /login . In the default configuration, it is the DefaultCredentialsToPrincipalResolver
| that fills this role. If you are using some other kind of credentials than UsernamePasswordCredentials, you will need to replace
| DefaultCredentialsToPrincipalResolver with a CredentialsToPrincipalResolver that supports the credentials you are
| using.
|
| Second, AuthenticationManagerImpl uses these resolvers to identify a service requesting a proxy granting ticket.
| In the default configuration, it is the HttpBasedServiceCredentialsToPrincipalResolver that serves this purpose.
| You will need to change this list if you are identifying services by something more or other than their callback URL.
+-->
<property name="credentialsToPrincipalResolvers">
<list>
<bean class="org.jasig.cas.authentication.principal.CredentialsToLDAPAttributePrincipalResolver">
<!-- The Principal resolver form the credentials -->
<property name="credentialsToPrincipalResolver">
<bean class="org.jasig.cas.authentication.principal.UsernamePasswordCredentialsToPrincipalResolver" >
<property name="attributeRepository">
<ref bean="attributeRepository" />
</property>
</bean>
</property>
<!-- The query made to find the Principal ID. "%u" will be replaced by the resolved Principal -->
<property name="filter" value="(|(IdNumber=%u)(sAMAccountName=%u)(mail=%u))" />
<!-- The attribute used to define the new Principal ID -->
<property name="principalAttributeName" value="IdNumber" />
<property name="searchBase" value="CN=Users,DC=middlebury,DC=edu"/>
<property name="contextSource" ref="contextSource" />
<property name="attributeRepository">
<ref bean="attributeRepository" />
</property>
</bean>
<bean class="org.jasig.cas.authentication.principal.CredentialsToLDAPAttributePrincipalResolver">
<!-- The Principal resolver form the credentials -->
<property name="credentialsToPrincipalResolver">
<bean class="org.jasig.cas.authentication.principal.UsernamePasswordCredentialsToPrincipalResolver" >
<property name="attributeRepository">
<ref bean="GuestAttributeRepository" />
</property>
</bean>
</property>
<!-- The query made to find the Principal ID. "%u" will be replaced by the resolved Principal -->
<property name="filter" value="(|(IdNumber=%u)(sAMAccountName=%u)(mail=%u))" />
<!-- The attribute used to define the new Principal ID -->
<property name="principalAttributeName" value="IdNumber" />
<property name="searchBase" value="OU=Guests,DC=middlebury,DC=edu"/>
<property name="contextSource" ref="contextSource" />
<property name="attributeRepository">
<ref bean="GuestAttributeRepository" />
</property>
</bean>
<!--
| UsernamePasswordCredentialsToPrincipalResolver supports the UsernamePasswordCredentials that we use for /login
| by default and produces SimplePrincipal instances conveying the username from the credentials.
|
| If you've changed your LoginFormAction to use credentials other than UsernamePasswordCredentials then you will also
| need to change this bean declaration (or add additional declarations) to declare a CredentialsToPrincipalResolver that supports the
| Credentials you are using.
+-->
<!-- <bean
class="org.jasig.cas.authentication.principal.UsernamePasswordCredentialsToPrincipalResolver" />
-->
<!--
| HttpBasedServiceCredentialsToPrincipalResolver supports HttpBasedCredentials. It supports the CAS 2.0 approach of
| authenticating services by SSL callback, extracting the callback URL from the Credentials and representing it as a
| SimpleService identified by that callback URL.
|
| If you are representing services by something more or other than an HTTPS URL whereat they are able to
| receive a proxy callback, you will need to change this bean declaration (or add additional declarations).
+-->
<bean
class="org.jasig.cas.authentication.principal.HttpBasedServiceCredentialsToPrincipalResolver" />
</list>
</property>
<!--
| Whereas CredentialsToPrincipalResolvers identify who it is some Credentials might authenticate,
| AuthenticationHandlers actually authenticate credentials. Here we declare the AuthenticationHandlers that
| authenticate the Principals that the CredentialsToPrincipalResolvers identified. CAS will try these handlers in turn
| until it finds one that both supports the Credentials presented and succeeds in authenticating.
+-->
<property name="authenticationHandlers">
<list>
<!--
| This is the authentication handler that authenticates services by means of callback via SSL, thereby validating
| a server side SSL certificate.
+-->
<bean class="org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandler">
<property name="httpClient" ref="httpClient" />
</bean>
<!--
| This is the authentication handler declaration that every CAS deployer will need to change before deploying CAS
| into production. The default SimpleTestUsernamePasswordAuthenticationHandler authenticates UsernamePasswordCredentials
| where the username equals the password. You will need to replace this with an AuthenticationHandler that implements your
| local authentication strategy. You might accomplish this by coding a new such handler and declaring
| edu.someschool.its.cas.MySpecialHandler here, or you might use one of the handlers provided in the adaptors modules.
+-->
<bean class="org.jasig.cas.adaptors.ldap.BindLdapAuthenticationHandler">
<property name="filter" value="(|(IdNumber=%u)(sAMAccountName=%u)(mail=%u))" />
<property name="searchBase" value="DC=middlebury,DC=edu" />
<property name="ignorePartialResultException" value="yes" />
<property name="contextSource" ref="contextSource" />
</bean>
</list>
</property>
</bean>
<!--
This bean defines the security roles for the Services Management application. Simple deployments can use the in-memory version.
More robust deployments will want to use another option, such as the Jdbc version.
The name of this should remain "userDetailsService" in order for Acegi to find it.
To use this, you should add an entry similar to the following between the two value tags:
battags=notused,ROLE_ADMIN
where battags is the username you want to grant access to. You can put one entry per line.
-->
<bean id="userDetailsService" class="org.springframework.security.userdetails.memory.InMemoryDaoImpl">
<property name="userMap">
<value>
<!-- Adam Franco -->
000000000=notused,ROLE_ADMIN
</value>
</property>
</bean>
<bean id="contextSource" class="org.jasig.cas.adaptors.ldap.util.AuthenticatedLdapContextSource">
<property name="pooled" value="false" />
<property name="urls">
<list>
<value>ldap://ad.middlebury.edu/</value>
</list>
</property>
<property name="userDn" value="xxxxxxxxx" />
<property name="password" value="yyyyyyyy" />
<property name="baseEnvironmentProperties">
<map>
<entry>
<key>
<value>java.naming.security.authentication</value>
</key>
<value>simple</value>
</entry>
</map>
</property>
</bean>
<!--
Bean that defines the attributes that a service may return. This example uses the Stub/Mock version. A real implementation
may go against a database or LDAP server. The id should remain "attributeRepository" though.
-->
<!--
Configuration updates by Adam (2009-03-11) based on example posted to the mailing list at:
https://lists.wisc.edu/read/messages?id=3079135#3079135
-->
<bean id="attributeRepository"
class="org.jasig.services.persondir.support.ldap.LdapPersonAttributeDao">
<property name="baseDN" value="CN=Users,DC=middlebury,DC=edu" />
<!-- This query is used to find the entry for populating attributes. {0} will be replaced by the new Principal ID extracted from the ldap -->
<property name="query" value="(|(IdNumber={0})(sAMAccountName={0})(mail={0}))" />
<property name="contextSource" ref="contextSource" />
<property name="ldapAttributesToPortalAttributes">
<map>
<!-- Mapping beetween LDAP entry's attributes (key) and Principal"s (value) -->
<entry key="IdNumber" value="Id" />
<entry key="givenName" value="FirstName" />
<entry key="sn" value="LastName" />
<entry key="mail" value="EMail" />
<entry key="sAMAccountName" value="Login" />
<entry key="telephoneNumber" value="TelephoneNumber" />
<entry key="memberOf" value="MemberOf" />
</map>
</property>
</bean>
<bean id="GuestAttributeRepository"
class="org.jasig.services.persondir.support.ldap.LdapPersonAttributeDao">
<property name="baseDN" value="OU=Guests,DC=middlebury,DC=edu" />
<!-- This query is used to find the entry for populating attributes. {0} will be replaced by the new Principal ID extracted from the ldap -->
<property name="query" value="(|(IdNumber={0})(sAMAccountName={0})(mail={0}))" />
<property name="contextSource" ref="contextSource" />
<property name="ldapAttributesToPortalAttributes">
<map>
<!-- Mapping beetween LDAP entry's attributes (key) and Principal"s (value) -->
<entry key="IdNumber" value="Id" />
<entry key="givenName" value="FirstName" />
<entry key="sn" value="LastName" />
<entry key="mail" value="EMail" />
<entry key="sAMAccountName" value="Login" />
<entry key="telephoneNumber" value="TelephoneNumber" />
<entry key="memberOf" value="MemberOf" />
</map>
</property>
</bean>
<!--
Sample, in-memory data store for the ServiceRegistry. A real implementation
would probably want to replace this with the JPA-backed ServiceRegistry DAO
The name of this bean should remain "serviceRegistryDao".
-->
<bean
id="serviceRegistryDao"
class="org.jasig.cas.services.JpaServiceRegistryDaoImpl"
p:entityManagerFactory-ref="entityManagerFactory" />
<bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
<property name="dataSource" ref="dataSource" />
<property name="jpaVendorAdapter">
<bean class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter">
<property name="generateDdl" value="true" />
<property name="showSql" value="true" />
</bean>
</property>
<property name="jpaProperties">
<props>
<prop key="hibernate.dialect">org.hibernate.dialect.MySQLDialect</prop>
<prop key="hibernate.hbm2ddl.auto">update</prop>
</props>
</property>
</bean>
<bean id="transactionManager" class="org.springframework.orm.jpa.JpaTransactionManager">
<property name="entityManagerFactory" ref="entityManagerFactory" />
</bean>
<tx:annotation-driven transaction-manager="transactionManager" />
<bean
id="dataSource"
class="org.apache.commons.dbcp.BasicDataSource"
p:driverClassName="com.mysql.jdbc.Driver"
p:url="jdbc:mysql://localhost:3306/cas?autoReconnect=true"
p:password="xxxxxxxxx"
p:username="yyyyyyyyy" />
</beans>
