CAS与LDAP整合的实现

原文地址：http://cxlh.javaeye.com/blog/257036

 

 

在做SOA项目或者单点登录的时候，用户目录往往都是通过LDAP来完成的，那么CAS与LDAP整合的问题是必须要做的，这里采用OpenLDAP和CAS来记录一下自己的配置过程

1. 下载CAS Server
2. 下载CAS Client
3. 下载OpenLDAP

都安装完成配置完成后，下面做CAS+OpenLDAP整合（至于配置过程，见我的另一篇博客文章：【推荐】单点登录的实现 ），在cas的web项目下打开：deployerConfigContext.xml，配置文件修改如下：

Xml代码

1. <?xml version="1.0" encoding="UTF-8"?>  
2. <!DOCTYPE beans PUBLIC  "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">  
3. <!--   
4.     | deployerConfigContext.xml centralizes into one file some of the declarative configuration that   
5.     | all CAS deployers will need to modify.   
6.     |   
7.     | This file declares some of the Spring-managed JavaBeans that make up a CAS deployment.     
8.     | The beans declared in this file are instantiated at context initialization time by the Spring    
9.     | ContextLoaderListener declared in web.xml.  It finds this file because this   
10.     | file is among those declared in the context parameter "contextConfigLocation".   
11.     |   
12.     | By far the most common change you will need to make in this file is to change the last bean   
13.     | declaration to replace the default SimpleTestUsernamePasswordAuthenticationHandler with   
14.     | one implementing your approach for authenticating usernames and passwords.   
15.     +-->  
16. <beans>  
17.     <!--   
18.         | This bean declares our AuthenticationManager.  The CentralAuthenticationService service bean   
19.         | declared in applicationContext.xml picks up this AuthenticationManager by reference to its id,    
20.         | "authenticationManager".  Most deployers will be able to use the default AuthenticationManager   
21.         | implementation and so do not need to change the class of this bean.  We include the whole   
22.         | AuthenticationManager here in the userConfigContext.xml so that you can see the things you will   
23.         | need to change in context.   
24.         +-->  
25.     <bean id="authenticationManager"  
26.         class="org.jasig.cas.authentication.AuthenticationManagerImpl">  
27.         <!--   
28.             | This is the List of CredentialToPrincipalResolvers that identify what Principal is trying to authenticate.   
29.             | The AuthenticationManagerImpl considers them in order, finding a CredentialToPrincipalResolver which    
30.             | supports the presented credentials.   
31.             |   
32.             | AuthenticationManagerImpl uses these resolvers for two purposes.  First, it uses them to identify the Principal   
33.             | attempting to authenticate to CAS /login .  In the default configuration, it is the DefaultCredentialsToPrincipalResolver   
34.             | that fills this role.  If you are using some other kind of credentials than UsernamePasswordCredentials, you will need to replace   
35.             | DefaultCredentialsToPrincipalResolver with a CredentialsToPrincipalResolver that supports the credentials you are   
36.             | using.   
37.             |   
38.             | Second, AuthenticationManagerImpl uses these resolvers to identify a service requesting a proxy granting ticket.    
39.             | In the default configuration, it is the HttpBasedServiceCredentialsToPrincipalResolver that serves this purpose.    
40.             | You will need to change this list if you are identifying services by something more or other than their callback URL.   
41.             +-->  
42.         <property name="credentialsToPrincipalResolvers">  
43.             <list>  
44.                 <!--   
45.                     | UsernamePasswordCredentialsToPrincipalResolver supports the UsernamePasswordCredentials that we use for /login    
46.                     | by default and produces SimplePrincipal instances conveying the username from the credentials.   
47.                     |    
48.                     | If you've changed your LoginFormAction to use credentials other than UsernamePasswordCredentials then you will also   
49.                     | need to change this bean declaration (or add additional declarations) to declare a CredentialsToPrincipalResolver that supports the   
50.                     | Credentials you are using.   
51.                     +-->  
52.                 <bean  
53.                     class="org.jasig.cas.authentication.principal.UsernamePasswordCredentialsToPrincipalResolver" />  
54.                 <!--   
55.                     | HttpBasedServiceCredentialsToPrincipalResolver supports HttpBasedCredentials.  It supports the CAS 2.0 approach of   
56.                     | authenticating services by SSL callback, extracting the callback URL from the Credentials and representing it as a   
57.                     | SimpleService identified by that callback URL.   
58.                     |   
59.                     | If you are representing services by something more or other than an HTTPS URL whereat they are able to   
60.                     | receive a proxy callback, you will need to change this bean declaration (or add additional declarations).   
61.                     +-->  
62.                 <bean  
63.                     class="org.jasig.cas.authentication.principal.HttpBasedServiceCredentialsToPrincipalResolver" />  
64.             </list>  
65.         </property>  
66.   
67.         <!--   
68.             | Whereas CredentialsToPrincipalResolvers identify who it is some Credentials might authenticate,    
69.             | AuthenticationHandlers actually authenticate credentials.  Here we declare the AuthenticationHandlers that   
70.             | authenticate the Principals that the CredentialsToPrincipalResolvers identified.  CAS will try these handlers in turn   
71.             | until it finds one that both supports the Credentials presented and succeeds in authenticating.   
72.             +-->  
73.         <property name="authenticationHandlers">  
74.             <list>  
75.                 <!--   
76.                     | This is the authentication handler that authenticates services by means of callback via SSL, thereby validating   
77.                     | a server side SSL certificate.   
78.                     +-->  
79.                 <bean  
80.                     class="org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandler" />  
81.   
82.                 <!--   
83.                     | This is the authentication handler declaration that every CAS deployer will need to change before deploying CAS    
84.                     | into production.  The default SimpleTestUsernamePasswordAuthenticationHandler authenticates UsernamePasswordCredentials   
85.                     | where the username equals the password.  You will need to replace this with an AuthenticationHandler that implements your   
86.                     | local authentication strategy.  You might accomplish this by coding a new such handler and declaring   
87.                     | edu.someschool.its.cas.MySpecialHandler here, or you might use one of the handlers provided in the adaptors modules.   
88.                     +-->  
89.                 <bean  
90.                     class="org.jasig.cas.adaptors.ldap.BindLdapAuthenticationHandler">  
91.                     <property name="filter" value="uid=%u" />  
92.                     <property name="searchBase" value="o=nbpt,c=cn" />    
93.                     <property  
94.                         name="contextSource"  
95.                         ref="contextSource" />  
96.                 </bean>  
97.             </list>  
98.         </property>  
99.     </bean>  
100.        
101.     <bean id="contextSource" class="org.jasig.cas.adaptors.ldap.util.AuthenticatedLdapContextSource">  
102.         <property name="anonymousReadOnly" value="false" />  
103.         <property name="password" value="password" />  
104.         <property name="pooled" value="true" />  
105.         <property name="urls">  
106.             <list>  
107.                 <value>ldap://localhost:389/</value>  
108.             </list>  
109.         </property>  
110.         <property name="userName" value="cn=manager,o=nbpt,c=cn" />  
111.         <property name="baseEnvironmentProperties">  
112.             <map>  
113.                 <entry>  
114.                         <key><value>java.naming.security.protocol</value></key>  
115.                         <value>none</value>  
116.                     </entry>  
117.                 <entry>  
118.                         <key><value>java.naming.security.authentication</value></key>  
119.                         <value>simple</value>  
120.                     </entry>  
121.                 </map>  
122.         </property>  
123.     </bean>  
124.   
125.     <!--   
126.     This bean defines the security roles for the Services Management application.  Simple deployments can use the in-memory version.   
127.     More robust deployments will want to use another option, such as the Jdbc version.   
128.        
129.     The name of this should remain "userDetailsService" in order for Acegi to find it.    
130.        
131.     To use this, you should add an entry similar to the following between the two value tags:   
132.     battags=notused,ROLE_ADMIN   
133.        
134.     where battags is the username you want to grant access to.  You can put one entry per line.   
135.      -->    
136.     <bean id="userDetailsService" class="org.springframework.security.userdetails.memory.InMemoryDaoImpl">  
137.         <property name="userMap">  
138.             <value>  
139.                
140.             </value>  
141.         </property>  
142.     </bean>    
143.        
144.     <!--    
145.     Bean that defines the attributes that a service may return.  This example uses the Stub/Mock version.  A real implementation   
146.     may go against a database or LDAP server.  The id should remain "attributeRepository" though.   
147.      -->  
148.     <bean id="attributeRepository"  
149.         class="org.jasig.services.persondir.support.StubPersonAttributeDao">  
150.         <property name="backingMap">  
151.             <map>  
152.                 <entry key="uid" value="uid" />  
153.                 <entry key="eduPersonAffiliation" value="eduPersonAffiliation" />    
154.                 <entry key="groupMembership" value="groupMembership" />  
155.             </map>  
156.         </property>  
157.     </bean>  
158.        
159.     <!--    
160.     Sample, in-memory data store for the ServiceRegistry. A real implementation   
161.     would probably want to replace this with the JPA-backed ServiceRegistry DAO   
162.     The name of this bean should remain "serviceRegistryDao".   
163.      -->  
164.     <bean  
165.         id="serviceRegistryDao"  
166.         class="org.jasig.cas.services.InMemoryServiceRegistryDaoImpl" />    
167. </beans>  

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC  "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">
<!--
	| 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>
	<!--
		| 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>
				<!--
					| 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" />

				<!--
					| 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="uid=%u" />
					<property name="searchBase" value="o=nbpt,c=cn" /> 
					<property
						name="contextSource"
						ref="contextSource" />
				</bean>
			</list>
		</property>
	</bean>
	
	<bean id="contextSource" class="org.jasig.cas.adaptors.ldap.util.AuthenticatedLdapContextSource">
		<property name="anonymousReadOnly" value="false" />
		<property name="password" value="password" />
		<property name="pooled" value="true" />
		<property name="urls">
			<list>
				<value>ldap://localhost:389/</value>
			</list>
		</property>
		<property name="userName" value="cn=manager,o=nbpt,c=cn" />
		<property name="baseEnvironmentProperties">
			<map>
				<entry>
				        <key><value>java.naming.security.protocol</value></key>
        				<value>none</value>
        			</entry>
				<entry>
				        <key><value>java.naming.security.authentication</value></key>
        				<value>simple</value>
        			</entry>
        		</map>
		</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>
			
		    </value>
		</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.
	 -->
	<bean id="attributeRepository"
		class="org.jasig.services.persondir.support.StubPersonAttributeDao">
		<property name="backingMap">
			<map>
				<entry key="uid" value="uid" />
				<entry key="eduPersonAffiliation" value="eduPersonAffiliation" /> 
				<entry key="groupMembership" value="groupMembership" />
			</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.InMemoryServiceRegistryDaoImpl" />	
</beans>

 在当前Web项目lib目录下cas-server-support-ldap-3.3.jar，spring-ldap-1.2.1.jar即可

我测试机器上LDAP数据如下：

其中LDAP中有一个用户名cxlh，密码为123的记录，那么在CAS登陆口输入cxlh/123，则转向登录成功页，如下图：

到此为止，配置完成！