<?xml version="1.0" encoding="UTF-8"?><!--
Licensed to Jasig under one or more contributor license
agreements. See the NOTICE file distributed withthis 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,WITHOUTWARRANTIESORCONDITIONSOFANYKIND, 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 inthis 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 inthis 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: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"><!--| 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
|interfacesupports plugging in another implementation, the default PolicyBasedAuthenticationManager should
| be sufficient in most cases.+--><!-- 认证管理器authenticationManager--><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 classis configured, you must explicitly
|set its name to something other than its defaultname(typically the simple classname).--><!-- 这个保留,试试去掉行不行:不影响登界面但是用户数据库认证还是通不过
<entry key-ref="proxyAuthenticationHandler" value-ref="proxyPrincipalResolver"/>--><!--这个被我注释掉了,20200703,目的是指定自己的本地数据库进行访问,
<entry key-ref="primaryAuthenticationHandler" value-ref="primaryPrincipalResolver"/>--><!--这个没调试好,只要打开网页就访问不到!!!!!!!!!!!! (因为dbAuthHandler里写的东西有问题,改了就好了)
第一个操作点!!!:key-ref指定自己的本地数据库访问,配置如下--><entry key-ref="dbAuthHandler" 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 withCAS:||* 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></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
--><!-- 下边这个配置是默认静态配置用户名和密码,那就在浏览器的CAS服务的登陆框中输入用户名casuser和密码Mellon,登录看看效果,就会出现验证成功的页面,如下图。你也可以在文件中自己配置自己的用户名和密码。
--><!--第二个操作点!!!:将默认的用户名和密码注释,其实上边的此种登陆方式已经被注释掉了,这里留着也没影响--><bean id="primaryAuthenticationHandler"class="org.jasig.cas.authentication.AcceptUsersAuthenticationHandler"><property name="users"><map><entry key="casuser" value="Mellon"/><entry key="admin" value="admin"/></map></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.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 thiswith the JPA-backed ServiceRegistry DAO
The name ofthis 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"/><!--
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><!-- 再在这个xml中新加入2个bean配置, 第三个操作点!!!:1、指定c3p0数据源(连接池);
注意,改了一下user,改成了username就会报404,所以必须是user --><bean id="dataSource"class="com.mchange.v2.c3p0.ComboPooledDataSource"
p:driverClass="com.mysql.jdbc.Driver"
p:jdbcUrl="jdbc:mysql://127.0.0.1:3306/myproject?characterEncoding=uft8"
p:user="root"
p:password="123123"/><!-- 第四个操作点!!!:2、查询匹配的字段。--><bean id="dbAuthHandler"class="org.jasig.cas.adaptors.jdbc.QueryDatabaseAuthenticationHandler"
p:dataSource-ref="dataSource"
p:sql="SELECT password FROM sec_user WHERE username = ?"/></beans>