Cas Server源碼編譯現場實例

　　最近公司有項目需要做單點登錄，根據要求就寫下這篇從github上下載的包到項目編譯通過，再到修改原代碼實現自己的特殊邏輯。

　　前提：

　　　　java環境

　　　　tomcat環境

　　　　maven環境

　　　　MyEclipse開發環境

　　一、cas項目構建方式匯總

　　cas-4.2.0以后(包括4.2.0)使用gradle構建

　　

 

 二、怎樣構建一個自定義的cas源碼項目

　　2.1 資源地址

　　　官網：https://www.apereo.org/projects/cas 

        源碼：https://github.com/Jasig/cas  

                https://github.com/Jasig/java-cas-client(后面要用到)

 

 　　 PS: 我這里演示的cas-server版本是Maven版的4.0.5

　　2.2 下載源碼並轉成項目代碼

　　　　從https://github.com/apereo/cas/releases?after=v4.1.0下載cas-4.0.5的源碼Source code (zip)，然后解壓放至你的workspace中。打開命令窗口，進入cas項目的根目錄(E:\me_workspace2\cas-4.0.5>)，鍵入命令mvn eclipse:eclipse,回車，讓它飛一會，結束后你就可以。然后你可以使用MyEclipse導入項目了，如下圖：

　　

　　2.3 將源碼編譯成war包

　　在命令窗口執行E:\me_workspace2\cas-4.0.5>mvn install -DskipTests，等待若干分鍾后\cas-4.0.5\cas-server-webapp\target\目錄下未發現生成cas.war 文件，並且發現下文的問題1，並且在問題1中得到你想要的war包。

     2.4 怎樣將構建一個帶有源碼的cas項目

　　將cas.war包修改擴展名，cas.zip，解壓。得到一堆文件。

　　新建一個Web項目，並將解壓好的文件放入項目中，\WEB-INF\classes目錄下文件統統放入src目錄下，其他的文件根據下圖自行拷貝。

　　

　　這樣的話，你就可以部署到Tomcat中運行了，localhost:8080/項目名。

　　2.5 新增數據庫

　　　　這里使用SQLserver數據庫，配置文件在WEB-INF目錄下的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: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
       | 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" />-->
                <!--接入自定義數據庫-->
                <entry key-ref="dbAuthenticationHandler" 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>
    </bean>

    <!-- Required for proxy ticket mechanism. -->
    <!--默認配置：開啟SSL-->
    <bean id="proxyAuthenticationHandler"
          class="org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandler"
          p:httpClient-ref="httpClient" />
    <!--新配置關閉SSL
    <bean id="proxyAuthenticationHandler"
          class="org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandler"
          p:httpClient-ref="httpClient" p:requireSecure="false"/>
    -->

    <!--
       | 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"/>
                <entry key="castest" value="castest"/>
            </map>
        </property>
    </bean>
    -->
      
    <bean class="org.jasig.cas.adaptors.jdbc.QueryDatabaseAuthenticationHandler">  
         <property name="sql" value="select password from ucenter_user where username=? " />  
         <property name="dataSource" ref="dataSource" />  
    </bean>
      
      
  <bean id="dataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource">
      <!--MySql數據庫認證-->
      <!-- 
      <property name="driverClassName"><value>com.mysql.jdbc.Driver</value></property>
       <property name="url"><value>jdbc:mysql://192.168.0.58:3306/cassso</value></property>
       <property name="username"><value>metro_monitor</value></property>
       <property name="password"><value>123456</value></property>
      -->
      <!--MsSql數據庫認證-->
       <property name="driverClassName"><value>com.microsoft.sqlserver.jdbc.SQLServerDriver</value></property>
       <property name="url"><value>jdbc:sqlserver://192.168.0.58:1433;DatabaseName=CasSso</value></property>
       <property name="username"><value>sa</value></property>
       <property name="password"><value>123456</value></property>
    </bean>

    <!--Mysql密碼加密-->
    <bean id="passwordEncoder"
      class="org.jasig.cas.authentication.handler.DefaultPasswordEncoder"
      c:encodingAlgorithm="MD5"
      p:characterEncoding="UTF-8" />

    <!--驗證處理-->
  <bean id="dbAuthenticationHandler"
    class="org.jasig.cas.adaptors.jdbc.QueryDatabaseAuthenticationHandler">
      <property name="dataSource" ref="dataSource"></property>
      <property name="sql" value="select LoginPassword as password from ssoaccount where LoginAccount=? "></property>
      <property name="passwordEncoder" ref="passwordEncoder"></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>
    -->
 <!-- 此處為增加部分 start -->  
    <bean id="attributeRepository" class="org.jasig.services.persondir.support.jdbc.SingleRowJdbcPersonAttributeDao" >  
        <constructor-arg index="0" ref="dataSource"/>  
        <constructor-arg index="1" value="SELECT * FROM ssoaccount WHERE {0}"/>  
        <property name="queryAttributeMapping">  
            <map>  
                <!-- key對應登錄信息， vlaue對應數據庫字段 -->  
                <entry key="username" value="LoginAccount"/>  
            </map>  
        </property>  
        <property name="resultAttributeMapping">  
            <map>  
                <!-- key對應數據庫字段  value對應attribute中的key -->  
                <entry key="Sex" value="Sex"/>  
                <entry key="Address" value="Address"/>  
            </map>  
        </property>  
    </bean>  
    <!-- 此處為增加部分 end --> 
    <!-- 
    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" />
        <!--
        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>

 

但是配置好后，編譯出現了問題，Error creating bean with name 'centralAuthenticationService' defined in .

這個問題是因為少了cas中jdbc的源碼，將上述mvn eclipse:eclipse編譯好的cas-server-support-jdbc項目導入Myeclipse中，並將項目中的代碼按現有目錄拷貝到Web項目中，

 

現項目圖片

最后編譯項目，打開項目地址，並輸入數據庫中的賬號與密碼，即可變廢為寶了。

再次就是其他4個jar的代碼，你可以通過拷貝的方式考入當前項目中。

問題1：

　　Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin

　　該問題是因為你想在源碼的根目錄直接運行編譯命令  C:\Users\Jadyer\Desktop\cas-4.0.5>mvn install -DskipTests  但最終沒發現\cas-4.0.5\cas-server-webapp\target\目錄下生成cas.war 文件

　　其實，是需要在 C:\Users\Jadyer\Desktop\cas-4.0.5\cas-server-webapp>目錄下執行該命令，才會生成war文件。如圖：

　　、

　　最后編譯了30分鍾

　　

 　　

　　最終是生成了一大堆文件

　　

查閱資料

　　http://blog.csdn.net/jadyer/article/details/46875393

　　http://blog.csdn.net/yanjunlu/article/details/45498509

　　http://blog.csdn.net/shadowsick/article/details/42191273

　　http://blog.csdn.net/small_love/article/details/6664831