- 浏览: 732497 次
- 性别:
- 来自: 宁波
文章分类
- 全部博客 (125)
- 软件开发 (17)
- java (32)
- js (2)
- jsp (1)
- struts2 (1)
- jquery (4)
- oracle (12)
- 程序员 (2)
- 三星i9300 联通版 root (1)
- easyui (2)
- DOM4J (2)
- 哲学 (1)
- ftp (1)
- oracle每日一学 (2)
- spring (4)
- jquery每日一学 (5)
- shiro (4)
- ITextRenderer (1)
- shiro标签 (1)
- mysql (1)
- mysql每日一学 (4)
- 分词 (1)
- vtiger crm (1)
- IkAnalyzer (1)
- jsoup (1)
- 多线程 (1)
- quartz (1)
- ubuntu (2)
- gradle学习笔记 (1)
- node.js (1)
- ajax (1)
- mybatis (1)
- cas (2)
- cxf (1)
- jqgrid (1)
- 开发工具破解 (1)
最新评论
-
氵每市蜃木娄:
使用过后,移动滚动条,非冻结的列,表头不见了。
easyui datagrid 右冻结 -
18335864773:
推荐用pageoffice组件打开文档,pageoffice ...
java word导出 -
xiaoliuf4565:
用过之后中文可以换行,但是现在编程了英文和数字不换行了脑壳痛
freemarker+ITextRenderer 生成html转pdf -
A741841403:
Error:(275, 29) java: 无法访问com.l ...
freemarker+ITextRenderer 生成html转pdf -
A741841403:
楼主你好,我想问下,如何在maven中使用你的jar包呢
freemarker+ITextRenderer 生成html转pdf
首先我用的是 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 来 群里 @ 我 我就是群主
相关推荐
CAS(Central Authentication Service)是一种基于Web的单一登录(Single Sign-On, SSO)协议,用于在网络上验证用户身份。它允许用户通过一个凭证(如用户名和密码)访问多个应用和服务,而无需为每个服务单独登录...
CAS 4.0.1是CAS的一个重要版本,它在4.0系列中引入了多项改进和新特性。通过分析其源代码,我们可以深入了解CAS的工作原理、架构设计以及如何自定义和扩展以满足特定需求。 【源码结构与模块】 CAS 4.0.1的源代码...
vmware horizon client 4.0.1 虚拟桌面客户端软件,用于与服务器连接
10. **监控与管理**:CAS管理界面可以查看当前在线用户、统计登录信息等,方便管理员监控系统状态。 综上所述,CAS-4.0.1是一个强大的SSO解决方案,它的设计和实现考虑了灵活性、可扩展性和安全性,适合各种规模的...
WinPcap 4.0.1 和 WpdPack 4.0.1 是两个重要的软件组件,主要用于网络数据包捕获和分析。在本文中,我们将深入探讨这两个工具的细节,以及它们在IT领域的应用。 首先,WinPcap是Windows平台上的一个开源库,全称为...
标题“STR-4.0.1DEMO”和描述中的信息相当简洁,只给出了一个版本号和可能的演示或示例的暗示。然而,通过标签“ST”,我们可以...如果你能够提供更多关于“STR-4.0.1DEMO”的具体信息,我可以提供更精确的知识点解释。
6. **图像读写改进**:OpenCV 4.0.1在图像读写方面进行了优化,支持更多的图像格式,处理速度更快,并且提供了更好的错误处理机制。 7. **视频处理**:视频处理模块在4.0.1版本中也有所增强,支持更多的视频编码和...
### Tornado 4.0.1 Python Framework Guide #### 用户指南 **1.1 引言** Tornado 是一个开源的 Python Web 框架,它以非阻塞的方式处理大量的并发连接,使得服务器能够高效地处理每一个客户端请求。Tornado 4.0.1...
"此版本没有短信bug"的描述,意味着用户在使用4.0.1版本时,可以期待一个稳定且可靠的短信服务,无需担心信息丢失、发送失败或延迟问题。 在Android平台上,短信功能的实现通常涉及与系统级SMS/MMS服务的交互,包括...
5. **兼容性改进**:R 4.0.1会保持对旧版代码的良好兼容性,同时可能会增加对新软件包的支持,使得用户可以使用更多最新的数据分析工具。 6. **编程环境的改进**:R Studio等R编程环境可能与新版本的R有更紧密的...
charles4.0.1破解补丁
官网下载更新日期2018.12.3,包含 poi-4.0.1.jar,poi-examples-4.0.1.jar,poi-excelant-4.0.1.jar,poi-ooxml-4.0.1.jar,poi-ooxml-schemas-4.0.1.jar,poi-scratchpad-4.0.1.jar;
总的来说,Firefox 4.0.1是一款集插件支持、性能优化、界面改进和增强安全于一体的浏览器版本,它不仅提升了用户的浏览体验,也为开发者提供了更强大的平台来创建和维护各种插件,进一步丰富了互联网生态。...
在4.0.1版本中,它支持多种认证策略,如基于表单的登录、HTTP基本认证和OAuth2。用户可以通过自定义AuthenticationProvider来实现自己的认证逻辑,或者使用内置的providers,如DaoAuthenticationProvider,该...
在Redis 4.0.1版本中,引入了多项改进和新特性,例如增加了一些新的命令,提高了性能,修复了已知的bug,并优化了集群的稳定性。这个版本的发布对于开发者来说是一个重要的里程碑,因为它提供了更好的可扩展性和可靠...
此外,"reddis4gem"可能是另一个与Redis相关的文件或目录,可能包含了配置文件、示例代码或其他辅助材料,帮助用户更好地理解和使用Redis。 总之,Redis作为一款强大的键值存储系统,通过其高效的数据结构和丰富的...
formValidator4.0.1通过JavaScript实现前端验证,可以在用户填写表单时立即给出反馈,无需等待服务器响应。这样可以显著提升用户界面的响应速度,同时也能减少由于错误数据导致的服务器错误。 此插件支持多种验证...
HttpClient 4.0.1所依赖的所有JAR包。包括: commons-logging-1.1.1.jar commons-codec-1.4.jar httpcore-4.0.1.jar<br/> httpclient-4.0.1.jar apache-mime4j-0.6.jar httpmime-4.0.1.jar
《SmartAdmin v4.0.1:重构版后台管理模板详解》 SmartAdmin v4.0.1是一款备受赞誉的后台管理模板,以其强大的功能、优雅的设计和易用性赢得了广大开发者的好评。这个版本是对其前代的全面重构,不仅优化了性能,还...
《Lily快捷启动管理工具4.0.1:打造个性化的高效工作平台》 在数字化时代,各种软件工具成为我们日常工作中不可或缺的一部分。然而,面对众多的应用程序,如何快速找到并启动我们需要的工具,成为了提高工作效率的...