CAS与LDAP整合的实现
在做SOA项目或者单点登录的时候，用户目录往往都是通过LDAP来完成的，那么CAS与LDAP整合的问题是必须要做的，这里采用OpenLDAP和CAS来记录一下自己的配置过程
都安装完成配置完成后，下面做CAS+OpenLDAP整合（至于配置过程，见我的另一篇博客文章：【推荐】单点登录的实现），在cas的web项目下打开：deployerConfigContext.xml，配置文件修改如下：
<?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"/><!--| 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/></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/><!--| 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.+--><beanvalue="uid=%u" /><property name="searchBase" value="o=nbpt,c=cn" /> <propertyname="contextSource"ref="contextSource" /></bean></list></property></bean><bean id="contextSource" 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_ADMINwhere battags is the username you want to grant access to. You can put one entry per line. --><bean id="userDetailsService" though. --><bean id="attributeRepository"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 implementationwould probably want to replace this with the JPA-backed ServiceRegistry DAOThe name of this bean should remain "serviceRegistryDao". --><beanid="serviceRegistryDao"/></beans>
?在当前Web项目lib目录下cas-server-support-ldap-3.3.jar，spring-ldap-1.2.1.jar即可
我测试机器上LDAP数据如下：
其中LDAP中有一个用户名cxlh，密码为123的记录，那么在CAS登陆口输入cxlh/123，则转向登录成功页，如下图：
到此为止，配置完成！
<bean id="contextSource" 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" /--> <!-- 如果您用的较新的版本，这里应该用的是userDn，而不是userName --> <property name="userDn" 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> <key><value>java.naming.security.protocol</value></key> <value>none</value><key><value>java.naming.security.protocol</value></key> <value>ssl</value>则端口应为636 10 楼 grandboy 2009-05-20 kiol 写道CAS能获取用户信息吗？
