cas4.0.1返回给客户端登陆用户的更多信息
首先我用的是 cas server 4.0.1版本的 网上不少都是 3.x的 我就不做考虑了
由于版本间配置差别太大
网上有关4.x的 配置资料太少 因此我在这里把这个博客写下 但愿对 跟我遇到相同问题的人有所帮助 同时也是对互联网的一种感恩回馈 由于我也是看了不少博客和资料后 才解决这个问题的
个人项目需求有点特殊 能够用邮箱和手机号码登陆
而登陆用的username又不是用的这两个字段 是经过一个值为uuid的 username字段实现的 （老项目重构 无法改表结构 ）
因此 光经过默认返回的 登陆帐号是不够的 由于 用户登陆后是能够修改邮箱和手机的 一旦修改后 个人 客户端获取就 会有问题
参考了 网上的
http://www.cnblogs.com/vhua/p/cas_4.html
http://www.tuicool.com/articles/QB3iia
这两个博客
第一个博客的方法没有 给出如何 用数据库的方式实现 以前在如何用jdbctemplate查询的时候一直 搞了好久没搞出来 参考了第二个博客后搞出来了
先把 deployerConfigContext.xml 贴出来
核心的 AccoutAttributeDao
protocol 2.0文件下 的 casServiceValidationSuccess.jsp页面加上
客户端调用
最后贴上客户端登陆后 得到的用户值的效果图
功夫不负有心人 终于解决这个问题了！ 若是看了个人博客 仍是没解决 能够 加扣扣群 186408628 来 群里 @ 我 我就是群主
由于版本间配置差别太大
网上有关4.x的 配置资料太少 因此我在这里把这个博客写下 但愿对 跟我遇到相同问题的人有所帮助 同时也是对互联网的一种感恩回馈 由于我也是看了不少博客和资料后 才解决这个问题的
个人项目需求有点特殊 能够用邮箱和手机号码登陆
而登陆用的username又不是用的这两个字段 是经过一个值为uuid的 username字段实现的 （老项目重构 无法改表结构 ）
因此 光经过默认返回的 登陆帐号是不够的 由于 用户登陆后是能够修改邮箱和手机的 一旦修改后 个人 客户端获取就 会有问题
参考了 网上的
http://www.cnblogs.com/vhua/p/cas_4.html
http://www.tuicool.com/articles/QB3iia
这两个博客
第一个博客的方法没有 给出如何 用数据库的方式实现 以前在如何用jdbctemplate查询的时候一直 搞了好久没搞出来 参考了第二个博客后搞出来了
先把 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 authentication handler 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:c="http://www.springframework.org/schema/c" xmlns:context="http://www.springframework.org/schema/context"
xmlns:tx="http://www.springframework.org/schema/tx" xmlns:util="http://www.springframework.org/schema/util"
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.2.xsd
http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-3.2.xsd
http://www.springframework.org/schema/security http://www.springframework.org/schema/security/spring-security-3.2.xsd
http://www.springframework.org/schema/util http://www.springframework.org/schema/util/spring-util.xsd
http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context.xsd">
<import resource="spring-configuration/propertyFileConfigurer.xml" />
<!-- | The authentication manager defines security policy for authentication
by specifying at a minimum | the authentication handlers that will be used
to authenticate credential. While the AuthenticationManager | interface supports
plugging in another implementation, the default PolicyBasedAuthenticationManager
should | be sufficient in most cases. + -->
<bean id="authenticationManager"
class="org.jasig.cas.authentication.PolicyBasedAuthenticationManager">
<constructor-arg>
<map>
<!-- | IMPORTANT | Every handler requires a unique name. | If more than
one instance of the same handler class is configured, you must explicitly
| set its name to something other than its default name (typically the simple
class name). -->
<entry key-ref="proxyAuthenticationHandler" value-ref="proxyPrincipalResolver" />
<entry key-ref="primaryAuthenticationHandler" value-ref="primaryPrincipalResolver" />
</map>
</constructor-arg>
<!-- Uncomment the metadata populator to allow clearpass to capture and
cache the password This switch effectively will turn on clearpass. <property
name="authenticationMetaDataPopulators"> <util:list> <bean class="org.jasig.cas.extension.clearpass.CacheCredentialsMetaDataPopulator"
c:credentialCache-ref="encryptedMap" /> </util:list> </property> -->
<!-- | Defines the security policy around authentication. Some alternative
policies that ship with CAS: | | * NotPreventedAuthenticationPolicy - all
credential must either pass or fail authentication | * AllAuthenticationPolicy
- all presented credential must be authenticated successfully | * RequiredHandlerAuthenticationPolicy
- specifies a handler that must authenticate its credential to pass -->
<property name="authenticationPolicy">
<bean class="org.jasig.cas.authentication.AnyAuthenticationPolicy" />
</property>
<property name="authenticationMetaDataPopulators">
<list>
<bean
class="org.jasig.cas.authentication.SuccessfulHandlerMetaDataPopulator" />
<bean
class="org.jasig.cas.authentication.principal.RememberMeAuthenticationMetaDataPopulator" />
</list>
</property>
</bean>
<!-- Required for proxy ticket mechanism. -->
<bean id="proxyAuthenticationHandler"
class="org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandler"
p:httpClient-ref="httpClient" />
<!-- | TODO: Replace this component with one suitable for your enviroment.
| | This component provides authentication for the kind of credential used
in your environment. In most cases | credential is a username/password pair
that lives in a system of record like an LDAP directory. | The most common
authentication handler beans: | | * org.jasig.cas.authentication.LdapAuthenticationHandler
| * org.jasig.cas.adaptors.jdbc.QueryDatabaseAuthenticationHandler | * org.jasig.cas.adaptors.x509.authentication.handler.support.X509CredentialsAuthenticationHandler
| * org.jasig.cas.support.spnego.authentication.handler.support.JCIFSSpnegoAuthenticationHandler -->
<!-- <bean id="primaryAuthenticationHandler" class="org.jasig.cas.authentication.AcceptUsersAuthenticationHandler">
<property name="users"> <map> <entry key="casuser" value="Mellon"/> </map>
</property> </bean> -->
<!-- 自定义数据库鉴权 -->
<!-- <bean id="primaryAuthenticationHandler" class="io.github.howiefh.cas.authentication.ValidUserQueryDBAuthenticationHandler">
<constructor-arg ref="dataSource" index="0"></constructor-arg> <constructor-arg
value="${auth.sql}" index="1"></constructor-arg> <constructor-arg value="MD5"
index="2"></constructor-arg> </bean> -->
<!-- 自定义数据库鉴权 -->
<bean id="primaryAuthenticationHandler"
class="io.github.howiefh.cas.authentication.ValidUserQueryDBAuthenticationHandler">
<constructor-arg ref="druidDataSource" index="0"></constructor-arg>
<constructor-arg value="${auth.sql}" index="1"></constructor-arg>
<constructor-arg value="${auth.sql_email}" index="2"></constructor-arg>
<constructor-arg value="${auth.sql_phone}" index="3"></constructor-arg>
<constructor-arg value="SHA1" index="4"></constructor-arg>
</bean>
<!-- 加密 -->
<!-- <property name="passwordEncoder" ref="myPasswordEncoder" /> -->
<!-- 密码不加密 -->
<bean id="myPasswordEncoder"
class="org.jasig.cas.authentication.handler.PlainTextPasswordEncoder" />
<!-- 密码加密 -->
<!-- <bean id="myPasswordEncoder" class="org.jasig.cas.authentication.handler.MyPasswordEncoder">
</bean> -->
<!-- 数据源 -->
<bean id="dataSource" class="com.alibaba.druid.pool.DruidDataSource"
init-method="init" destroy-method="close">
<property name="driverClassName" value="${dataSource.driver}"></property>
<property name="url" value="${dataSource.url}" />
<property name="username" value="${dataSource.username}" />
<property name="password" value="${dataSource.password}" />
<property name="maxActive" value="${dataSource.maxActive}" />
<property name="initialSize" value="${dataSource.initialSize}" />
<property name="maxWait" value="${dataSource.maxWait}" />
<property name="minIdle" value="${dataSource.minIdle}" />
<property name="timeBetweenEvictionRunsMillis" value="${dataSource.timeBetweenEvictionRunsMillis}" />
<property name="minEvictableIdleTimeMillis" value="${dataSource.minEvictableIdleTimeMillis}" />
<property name="validationQuery" value="${dataSource.validationQuery}" />
<property name="testWhileIdle" value="${dataSource.testWhileIdle}" />
<property name="testOnBorrow" value="${dataSource.testOnBorrow}" />
<property name="testOnReturn" value="${dataSource.testOnReturn}" />
<property name="maxOpenPreparedStatements" value="${dataSource.maxOpenPreparedStatements}" />
<property name="removeAbandoned" value="${dataSource.removeAbandoned}" /> <!-- 打开removeAbandoned功能 -->
<property name="removeAbandonedTimeout" value="${dataSource.removeAbandonedTimeout}" /> <!-- 1800秒，也就是30分钟 -->
<property name="logAbandoned" value="${dataSource.logAbandoned}" /> <!-- 关闭abanded链接时输出错误日志 -->
</bean>
<!-- <bean id="myjdbctemplate" class="org.springframework.jdbc.core.JdbcTemplate">
<property name="dataSource"> <ref local="druidDataSource" /> </property>
</bean> -->
<bean id="jdbcTemplate" class="org.springframework.jdbc.core.JdbcTemplate">
<property name="dataSource" ref="druidDataSource"/>
</bean>
<!-- 配置 Spring 使用的数据源 -->
<bean id="druidDataSource" class="com.alibaba.druid.pool.DruidDataSource"
init-method="init" destroy-method="close">
<property name="dbType" value="sqlserver" />
<!-- 基本属性配置 -->
<property name="url" value="${datasource2.url}" />
<property name="username" value="${datasource2.username}" />
<property name="password" value="${datasource2.password}" />
<!-- 配置初始化大小、最小、最大 -->
<property name="initialSize" value="10" />
<property name="minIdle" value="5" />
<property name="maxActive" value="20" />
<!-- 配置获取链接等待超时的时间 -->
<property name="maxWait" value="60000" />
<!-- 配置间隔多久才进行一次检测，检测须要关闭的空闲链接，单位是毫秒 -->
<property name="timeBetweenEvictionRunsMillis" value="60000" />
<!-- 配置一个链接在池中最小生存的时间，单位是毫秒 -->
<property name="minEvictableIdleTimeMillis" value="300000" />
<!-- <property name="validationQuery" value="SELECT 'x'" /> <property name="testWhileIdle"
value="true" /> <property name="testOnBorrow" value="false" /> <property
name="testOnReturn" value="false" /> -->
<!-- 打开PSCache，而且指定每一个链接上PSCache的大小 <property name="poolPreparedStatements"
value="false" /> <property name="maxPoolPreparedStatementPerConnectionSize"
value="20" /> -->
<!-- 配置监控统计拦截的filters -->
<property name="filters" value="stat,wall" />
<!-- 合并sql -->
<property name="proxyFilters">
<list>
<ref bean="stat-filter" />
</list>
</property>
</bean>
<bean id="stat-filter" class="com.alibaba.druid.filter.stat.StatFilter">
<property name="slowSqlMillis" value="10000" />
<property name="logSlowSql" value="true" />
</bean>
<!-- <bean id="dataSource_sqlserver" class="org.apache.commons.dbcp.BasicDataSource"
destroy-method="close"> <property name="driverClassName"> <value>com.microsoft.sqlserver.jdbc.SQLServerDriver</value>
</property> <property name="url"> <value>jdbc:sqlserver://localhost:1433;database=Z_MARK_MANAGE;integratedSecurity=false</value>
</property> <property name="username"> <value>sa</value> </property> <property
name="password"> <value>wellhope</value> </property> <property name="validationQuery">
<value>select count(*) from [Z_MARK_MANAGE].[dbo].[USER_INFO]</value> </property>
</bean> -->
<!-- Required for proxy ticket mechanism -->
<bean id="proxyPrincipalResolver"
class="org.jasig.cas.authentication.principal.BasicPrincipalResolver" />
<!-- | Resolves a principal from a credential using an attribute repository
that is configured to resolve | against a deployer-specific store (e.g. LDAP). -->
<bean id="primaryPrincipalResolver"
class="org.jasig.cas.authentication.principal.PersonDirectoryPrincipalResolver">
<property name="attributeRepository" ref="attributeRepository" />
</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.AccoutAttributeDao" >
<property name="jdbcTemplate" ref="jdbcTemplate"/>
</bean>
<!--修改后 end-->
<!-- 修改前 -->
<!-- <bean id="attributeRepository" class="org.jasig.services.persondir.support.StubPersonAttributeDao"
p:backingMap-ref="attrRepoBackingMap" /> <util:map id="attrRepoBackingMap">
<entry key="uid" value="uid" /> <entry key="eduPersonAffiliation" value="eduPersonAffiliation"
/> <entry key="groupMembership" value="groupMembership" /> </util:map>
-->
<!-- 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"
p:registeredServices-ref="registeredServicesList" />
<util:list id="registeredServicesList">
<!-- 修改前 -->
<bean class="org.jasig.cas.services.RegexRegisteredService" p:id="0"
p:name="HTTP and IMAP" p:description="Allows HTTP(S) and IMAP(S) protocols"
p:serviceId="^(https?|imaps?)://.*" p:evaluationOrder="10000001" />
<!-- 修改后 -->
<!-- <bean class="org.jasig.cas.services.RegexRegisteredService" p:id="0"
p:name="HTTP and IMAP" p:description="Allows HTTP(S) and IMAP(S) protocols"
p:serviceId="^(https?|imaps?)://.*" p:evaluationOrder="10000001" >
<property name="allowedAttributes">
<list>
<value>id</value>
<value>username</value>
<value>email</value>
<value>phonenumber</value>
</list>
</property>
</bean> -->
<!-- <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?)://.*" />
<property name="evaluationOrder" value="0" />
<property name="allowedAttributes">
<list>
<value>id</value>
<value>username</value>
<value>email</value>
<value>phonenumber</value>
</list>
</property>
</bean>
-->
<!-- 支持代理 --><!-- p:enabled=”true” p:allowedToProxy=”true” p:ssoEnabled=”true” -->
<!-- Use the following definition instead of the above to further restrict
access to services within your domain (including sub domains). Note that
example.com must be replaced with the domain you wish to permit. This example
also demonstrates the configuration of an attribute filter that only allows
for attributes whose length is 3. -->
<!-- <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" /> <property name="attributeFilter">
<bean class="org.jasig.cas.services.support.RegisteredServiceRegexAttributeFilter"
c:regex="^\w{3}$" /> </property> </bean> -->
</util:list>
<bean id="auditTrailManager"
class="com.github.inspektr.audit.support.Slf4jLoggingAuditTrailManager" />
<bean id="healthCheckMonitor" class="org.jasig.cas.monitor.HealthCheckMonitor"
p:monitors-ref="monitorsList" />
<util:list id="monitorsList">
<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" />
</util:list>
</beans>
核心的 AccoutAttributeDao
package org.jasig.services.persondir.support;
import java.util.Collections;
import java.util.HashMap;
import java.util.List;
import java.util.Map;
import org.jasig.services.persondir.IPersonAttributes;
import org.springframework.jdbc.core.JdbcTemplate;
public class AccoutAttributeDao extends StubPersonAttributeDao {
private JdbcTemplate jdbcTemplate;
public JdbcTemplate getJdbcTemplate() {
return jdbcTemplate;
}
public void setJdbcTemplate(JdbcTemplate jdbcTemplate) {
this.jdbcTemplate = jdbcTemplate;
}
@Override
public IPersonAttributes getPerson(String uid) {
String sql = "";
if (uid.indexOf("@") > 0) { // 若是是邮箱
sql = "select * from Account where email=?";
} else {
sql = "select * from Account where PhoneNumber=?";
}
//
final Map<String, Object> values = jdbcTemplate.queryForMap(sql, uid);
Map<String, List<Object>> attributes = new HashMap<String, List<Object>>();
attributes.put("username",
Collections.singletonList((Object) values.get("UserName")));
attributes.put("email",
Collections.singletonList((Object) values.get("Email")));
attributes.put("phonenumber",
Collections.singletonList((Object) values.get("PhoneNumber")));
attributes.put("id",
Collections.singletonList((Object) values.get("Id")));
return new AttributeNamedPersonImpl(attributes);
}
}
protocol 2.0文件下 的 casServiceValidationSuccess.jsp页面加上
<c:if test="${fn:length(assertion.chainedAuthentications[fn:length(assertion.chainedAuthentications)-1].principal.attributes) > 0}">
<cas:attributes>
<c:forEach var="attr" items="${assertion.chainedAuthentications[fn:length(assertion.chainedAuthentications)-1].principal.attributes}">
<cas:${fn:escapeXml(attr.key)}>${fn:escapeXml(attr.value)}</cas:${fn:escapeXml(attr.key)}>
</c:forEach>
</cas:attributes>
</c:if>
客户端调用
package com.gttown.app.user.controller;
import java.util.Map;
import javax.servlet.http.HttpServletRequest;
import org.jasig.cas.client.authentication.AttributePrincipal;
import org.jasig.cas.client.util.AssertionHolder;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.stereotype.Controller;
import com.gttown.app.user.model.Account;
import com.gttown.app.user.service.AccountService;
@Controller
public class BaseController {
@Autowired
private AccountService accountService;
/**
* 获取当前登陆用户帐号信息
*/
public Account getAccount(HttpServletRequest request) {
// String loginaccount =
// AssertionHolder.getAssertion().getPrincipal().getName(); //登陆帐号
//
//
AttributePrincipal principal = (AttributePrincipal) request
.getUserPrincipal();
Map attributes = principal.getAttributes();
// Map attributes2 =
// AssertionHolder.getAssertion().getPrincipal().getAttributes();
//
String id = (String) attributes.get("id");
String uuid = (String) attributes.get("username"); // 惟一key uuid
System.out.println(uuid);
String email = (String) attributes.get("email");
String phonenumber = (String) attributes.get("phonenumber");
Account account = new Account();
account.setId(new Long(id));
account.setEmail(email);
account.setPhonenumber(phonenumber);
account.setUsername(uuid);
return account;
}
}
最后贴上客户端登陆后 得到的用户值的效果图
功夫不负有心人 终于解决这个问题了！ 若是看了个人博客 仍是没解决 能够 加扣扣群 186408628 来 群里 @ 我 我就是群主
相关文章
- 1. cas4.0.1返回给客户端登陆用户的更多信息
- 2. cas 3.5.2 返回用户更多信息
- 3. cas4.0 session中返回更多的用户信息
- 4. ASP.NET MVC用户登陆(Memcache存储用户登陆信息)
- 5. 用户登陆并返回token（springboot）
- 6. 让cas-service 返回更多用户信息
- 7. 使用Socket实现多客户端用户登陆
- 8. android客户端登陆成功后，在本地保存用户信息
- 9. CAS学习笔记（三）—— SERVER登陆后用户信息的返回
- 10. cas获取返回用户信息
- 更多相关文章...
- • XSLT - 在客户端 - XSLT 教程
- • MySQL客户端和服务器端工具集 - MySQL教程
- • 算法总结-回溯法
- • C# 中 foreach 遍历的用法
相关标签/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
欢迎关注本站公众号,获取更多信息
