单点登录实现方式
运营中心系统采用Cas（全称是Centeral Authentication Service）作为单点登录SSO（Single Sign
On）的实现方式。其由Cas Server和Cas Client两部分组成，Cas Server是核心，而Cas
Client通常对应于我们的应用系统。一个Cas Server可以对应多个Cas
Client。它允许我们在一个Client进行登录以后无需再让用户输入用户名和密码进行认证即可访问其它Client应用。
由于运营中心系统和国药健康在线大部分业务系统都使用Spring Security来管理用户、角色和权限。所以需要在各业务系统的Spring
Security应用中整合Cas Client，以达到使用Cas Server实现单点登录和登出的效果。
客户端项目配置
- 配置依赖jar包 首先需要将Spring Security对Cas支持的jar包加入到应用的类路径中。如果我们的应用是用Maven构造的，则可以在应用的pom.xml文件中加上如下依赖。
<!-- Spring Security cas-->
<dependency>
<groupId>org.springframework.security</groupId>
<artifactId>spring-security-cas</artifactId>
<version>3.1.4.RELEASE</version>
</dependency>
<dependency>
<groupId>org.jasig.cas.client</groupId>
<artifactId>cas-client-core</artifactId>
<version>3.2.1</version>
</dependency>
<dependency>
<groupId>net.sf.ehcache</groupId>
<artifactId>ehcache</artifactId>
<version>2.10.0</version>
</dependency>
<!-- Spring Security cas-->添加证书到信任库
在Cas单点登录验证过程中，还需要验证证书，这需要我们将之前建立的证书导出并添加到当前运行时使用的JRE的证书信任库中。可直接使用如下命令和证书文件导入。
keytool -import cert -alias cas -file cas.crt -keystore
“%JAVA_HOME%\jre\lib\security\cacerts” -storepass changeit –nopromptHOSTS文件配置 如果Cas
Server、运营中心系统，以及对接业务系统运行在局域网内，没有各自的域名映射，则需要通过修改HOSTS文件配置的方式，添加各个系统的域名映射关系。且除Cas
Server不需要配置自己的域名外，其它各系统域名在各个服务器上均需配置全部域名映射，且各域名映射需保持一致。如测试环境下，运营中心系统的hosts文件配置：#Cas Server域名
192.168.1.132 cas.suse.server
#项目域名
192.168.1.201 cas.auth.com在web.xml中配置单点监听类
<listener>
<listener-class>org.jasig.cas.client.session.SingleSignOutHttpSessionListener</listener-class>
</listener>添加spring-cas.xml单点登陆的客户端配置文件
将之前的spring-security.xml配置文件,改成spring-cas.xml配置文件,使spring容器加载单点的配置文件
<?xml version="1.0" encoding="UTF-8"?>
<beans:beans xmlns="http://www.springframework.org/schema/security"
xmlns:beans="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/security
http://www.springframework.org/schema/security/spring-security.xsd">
<!--################### 资源css,jsp,jpeg,js##################### -->
<!-- <http pattern="/styles/**" security="none"></http> -->
<http pattern="/**/*.css" security="none"/>
<http pattern="/**/*.js" security="none"/>
<http pattern="/**/*.jpg" security="none"/>
<http pattern="/**/*.png" security="none"/>
<http pattern="/**/*.gif" security="none"/>
<http pattern="/**/*.swf" security="none"/>
<http pattern="/**/*.xml" security="none"/>
<!-- ########################################################### -->
<!-- #####################登陆页,和拒绝页,超时页 #####################-->
<!-- <http pattern="/login.jsp" security="none"></http> -->
<http pattern="/access.jsp" security="none" />
<http pattern="/sessionTimeOut.jsp" security="none"></http>
<!-- ############################################################ -->
<!--SSO -->
<http auto-config="false" entry-point-ref="casEntryPoint" servlet-api-provision="true">
<!--校验登陆可访问-->
<intercept-url pattern="/login.jsp" access="IS_AUTHENTICATED_FULLY" />
<intercept-url pattern="/permission/index.do" access="IS_AUTHENTICATED_FULLY" />
<intercept-url pattern="/permission/user.do?method=checkUserNameById" access="IS_AUTHENTICATED_FULLY" />
<intercept-url pattern="/permission/user.do?method=checkUserName" access="IS_AUTHENTICATED_FULLY" />
<intercept-url pattern="/permission/role.do?method=checkName" access="IS_AUTHENTICATED_FULLY" />
<intercept-url pattern="/permission/role.do?method=checkNameById" access="IS_AUTHENTICATED_FULLY" />
<intercept-url pattern="/permission/permission.do?method=checkNameById" access="IS_AUTHENTICATED_FULLY" />
<intercept-url pattern="/permission/permission.do?method=checkUrlById" access="IS_AUTHENTICATED_FULLY" />
<intercept-url pattern="/permission/permission.do?method=checkName" access="IS_AUTHENTICATED_FULLY" />
<intercept-url pattern="/permission/permission.do?method=checkUrl" access="IS_AUTHENTICATED_FULLY" />
<session-management invalid-session-url="http://cas.auth.com:8080/auth/permission/index.do" session-fixation-protection="none" >
<concurrency-control max-sessions="1" error-if-maximum-exceeded="false" expired-url="http://cas.auth.com:8080/auth/permission/index.do" />
</session-management>
<custom-filter position="CAS_FILTER" ref="casFilter" />
<custom-filter ref="requestSingleLogoutFilter" before="LOGOUT_FILTER" />
<custom-filter ref="singleLogoutFilter" before="CAS_FILTER" />
<logout logout-url="/logout" logout-success-url="https://cas.suse.server:8443/cas/logout?service=http://cas.auth.com:8080/auth" />
</http>
<!-- CAS认证切入点，声明cas服务器端登录的地址 -->
<beans:bean id="casEntryPoint" class="org.springframework.security.cas.web.CasAuthenticationEntryPoint">
<beans:property name="loginUrl" value="https://cas.suse.server:8443/cas/login" />
<beans:property name="serviceProperties" ref="serviceProperties" />
</beans:bean>
<!-- 登录成功后的返回地址 -->
<beans:bean id="serviceProperties" class="org.springframework.security.cas.ServiceProperties">
<!-- Cas Server认证成功后的跳转地址，这里要跳转到我们的Spring Security应用，之后会由CasAuthenticationFilter处理，默认处理地址为/j_spring_cas_security_check -->
<beans:property name="service" value="http://cas.auth.com:8080/auth/j_spring_cas_security_check" />
<beans:property name="sendRenew" value="false" />
</beans:bean>
<!-- cas 认证过滤器 -->
<beans:bean id="casFilter" class="org.springframework.security.cas.web.CasAuthenticationFilter">
<beans:property name="authenticationManager" ref="authenticationManager" />
<beans:property name="authenticationFailureHandler" ref="authenticationFailureHandler" />
<beans:property name="authenticationSuccessHandler" ref="authenticationSuccessHandler" />
<beans:property name="filterProcessesUrl" value="/j_spring_cas_security_check"/>
<!-- cas 代理端配置 -->
<beans:property name="proxyGrantingTicketStorage" ref="pgtStorage"/>
<beans:property name="proxyReceptorUrl" value="/proxyreceptor"/>
<!-- cas 代理端配置 -->
</beans:bean>
<!-- cas 认证失败控制器 -->
<beans:bean id="authenticationFailureHandler" class="org.springframework.security.web.authentication.SimpleUrlAuthenticationFailureHandler">
<beans:property name="defaultFailureUrl" value="/access.jsp" />
</beans:bean>
<!-- cas 认证成功控制器 -->
<beans:bean id="authenticationSuccessHandler" class="org.springframework.security.web.authentication.SimpleUrlAuthenticationSuccessHandler">
<beans:property name="alwaysUseDefaultTargetUrl" value="true" />
<beans:property name="defaultTargetUrl" value="/permission/index.do" />
</beans:bean>
<!-- 注销客户端 -->
<beans:bean id="singleLogoutFilter" class="org.jasig.cas.client.session.SingleSignOutFilter" />
<!-- 注销服务器端 -->
<beans:bean id="requestSingleLogoutFilter" class="org.springframework.security.web.authentication.logout.LogoutFilter">
<beans:constructor-arg value="https://cas.suse.server:8443/cas/logout" />
<beans:constructor-arg>
<beans:bean class="org.springframework.security.web.authentication.logout.SecurityContextLogoutHandler" />
</beans:constructor-arg>
<beans:property name="filterProcessesUrl" value="/j_spring_cas_security_logout" />
</beans:bean>
<!-- 在认证管理器中注册cas认证提供器 -->
<authentication-manager alias="authenticationManager">
<authentication-provider ref="casAuthenticationProvider" />
</authentication-manager>
<!-- cas认证提供器，定义客户端的验证方式 -->
<beans:bean id="casAuthenticationProvider" class="org.springframework.security.cas.authentication.CasAuthenticationProvider">
<beans:property name="authenticationUserDetailsService" ref="casAuthenticationUserDetailsService" />
<beans:property name="serviceProperties" ref="serviceProperties" />
<!-- 配置TicketValidator在登录认证成功后验证ticket -->
<beans:property name="ticketValidator">
<beans:bean class="org.jasig.cas.client.validation.Cas20ProxyTicketValidator">
<!-- Cas Server访问地址的前缀，即根路径-->
<beans:constructor-arg index="0" value="https://cas.suse.server:8443/cas" />
<!-- cas 代理端配置 -->
<beans:property name="allowedProxyChains" value="http://cas.auth.com:8080/auth/proxyreceptor"/>
<beans:property name="proxyCallbackUrl" value="http://cas.auth.com:8080/auth/proxyreceptor"/>
<beans:property name="proxyGrantingTicketStorage" ref="pgtStorage"/>
<beans:property name="acceptAnyProxy" value="true"/>
<!-- /cas 代理端配置 -->
</beans:bean>
</beans:property>
<beans:property name="key" value="key4CasAuthenticationProvider" />
<beans:property name="statelessTicketCache">
<beans:bean class="org.springframework.security.cas.authentication.EhCacheBasedTicketCache">
<beans:property name="cache">
<beans:bean class="net.sf.ehcache.Cache" init-method="initialise" destroy-method="dispose">
<beans:constructor-arg value="casTickets"/>
<beans:constructor-arg value="50"/>
<beans:constructor-arg value="true"/>
<beans:constructor-arg value="false"/>
<beans:constructor-arg value="3600"/>
<beans:constructor-arg value="900"/>
<beans:property name="cacheManager">
<beans:bean class="org.springframework.cache.ehcache.EhCacheManagerFactoryBean"/>
</beans:property>
</beans:bean>
</beans:property>
</beans:bean>
</beans:property>
</beans:bean>
<!-- 标注pgtStorage -->
<beans:bean id="pgtStorage" class="org.jasig.cas.client.proxy.ProxyGrantingTicketStorageImpl"/>
<!-- 通过username来加载UserDetails -->
<beans:bean id="casAuthenticationUserDetailsService" class="org.springframework.security.core.userdetails.UserDetailsByNameServiceWrapper">
<beans:property name="userDetailsService">
<!-- 真正加载UserDetails的UserDetailsService实现 -->
<beans:ref local="userServiceDetail"/>
</beans:property>
</beans:bean>
<!-- 注册userServiceDetail -->
<beans:bean id="userServiceDetail"
class="com.yao123.auth.web.secure.api.MyUserDetailServiceImpl">
</beans:bean>
</beans:beans>
服务器端CAS配置
1. 修改单点的配置文件deployerConfigContext.xml
<?xml version="1.0" encoding="UTF-8"?>
<!--
Licensed to Jasig under one or more contributor license
agreements. See the NOTICE file distributed with this work
for additional information regarding copyright ownership.
Jasig licenses this file to you under the Apache License,
Version 2.0 (the "License"); you may not use this file
except in compliance with the License. You may obtain a
copy of the License at the following location:
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
| 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:p="http://www.springframework.org/schema/p"
xmlns:tx="http://www.springframework.org/schema/tx"
xmlns:sec="http://www.springframework.org/schema/security"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.1.xsd
http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-3.1.xsd
http://www.springframework.org/schema/security http://www.springframework.org/schema/security/spring-security-3.1.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">
<!-- Uncomment the metadata populator to allow clearpass to capture and cache the password
This switch effectively will turn on clearpass.
<property name="authenticationMetaDataPopulators">
<list>
<bean class="org.jasig.cas.extension.clearpass.CacheCredentialsMetaDataPopulator">
<constructor-arg index="0" ref="credentialsCache" />
</bean>
</list>
</property>
-->
<!--
| 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" >
<property name="attributeRepository" ref="attributeRepository" />
</bean>
<!--
| 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"
p:httpClient-ref="httpClient" p:requireSecure="false"/>
<!--
| 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.authentication.handler.support.SimpleTestUsernamePasswordAuthenticationHandler" />
<bean class="org.jasig.cas.adaptors.jdbc.QueryDatabaseAuthenticationHandler">
<property name="dataSource" ref="dataSource"></property>
<property name="sql" value="select userPassword from user where userName=?"></property>
<property name="passwordEncoder" ref="MinxinLoan5CASMD5"></property>
</bean>
-->
<bean class="org.jasig.cas.adaptors.jdbc.QueryDatabaseAuthenticationHandler">
<property name="dataSource" ref="dataSource" ></property>
<property name="sql" value="select password from `user` where username=? and status=1" ></property>
<property name="passwordEncoder" ref="MD5PasswordEncoder" ></property>
</bean>
</list>
</property>
</bean>
<!--数据源信息-->
<bean id="dataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource">
<property name="driverClassName" value="com.mysql.jdbc.Driver" />
<property name="url" value="jdbc:mysql://数据库IP:3306/auth2?characterEncoding=UTF-8" />
<property name="username" value="root" />
<property name="password" value="" />
</bean>
<bean id="MD5PasswordEncoder" class="org.jasig.cas.authentication.handler.DefaultPasswordEncoder">
<constructor-arg index="0" value="MD5" />
</bean>
<!--自定义加密类-->
<!--<bean id="passwordEncoder" class="com.guoyao.encrypt.MinxinLoan5CASMD5"></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 Spring Security to find it.
-->
<!-- <sec:user name="@@THIS SHOULD BE REPLACED@@" password="notused" authorities="ROLE_ADMIN" />-->
<sec:user-service id="userDetailsService">
<sec:user name="@@THIS SHOULD BE REPLACED@@" password="notused" authorities="ROLE_ADMIN" />
</sec:user-service>
<!--
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">
<property name="registeredServices">
<list>
<bean class="org.jasig.cas.services.RegexRegisteredService">
<property name="id" value="0" />
<property name="name" value="HTTP and IMAP" />
<property name="description" value="Allows HTTP(S) and IMAP(S) protocols" />
<property name="serviceId" value="^(https?|imaps?)://.*" />
<property name="evaluationOrder" value="10000001" />
</bean>
<!--
Use the following definition instead of the above to further restrict access
to services within your domain (including subdomains).
Note that example.com must be replaced with the domain you wish to permit.
-->
<!--
<bean class="org.jasig.cas.services.RegexRegisteredService">
<property name="id" value="1" />
<property name="name" value="HTTP and IMAP on example.com" />
<property name="description" value="Allows HTTP(S) and IMAP(S) protocols on example.com" />
<property name="serviceId" value="^(https?|imaps?)://([A-Za-z0-9_-]+\.)*example\.com/.*" />
<property name="evaluationOrder" value="0" />
</bean>
-->
</list>
</property>
</bean>
<bean id="auditTrailManager" class="com.github.inspektr.audit.support.Slf4jLoggingAuditTrailManager" />
<bean id="healthCheckMonitor" class="org.jasig.cas.monitor.HealthCheckMonitor">
<property name="monitors">
<list>
<bean class="org.jasig.cas.monitor.MemoryMonitor"
p:freeMemoryWarnThreshold="10" />
<!--
NOTE
The following ticket registries support SessionMonitor:
* DefaultTicketRegistry
* JpaTicketRegistry
Remove this monitor if you use an unsupported registry.
-->
<bean class="org.jasig.cas.monitor.SessionMonitor"
p:ticketRegistry-ref="ticketRegistry"
p:serviceTicketCountWarnThreshold="5000"
p:sessionCountWarnThreshold="100000" />
</list>
</property>
</bean>
</beans>
2.在单点的cas.war解压开的cas项目中的lib下增加mysql 驱动jar包 ,以及单点支持jdbc的jar包cas-server-support-jdbc-3.5.1
至此单点登陆的搭建及配置完成感谢同行的小伙伴们查阅!
513
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
