BlogJava-无极，无际，无迹-文章分类-软件架构

SpringSecurity使用记录（六）-- 本地配置二

taochen — Mon, 25 Jan 2010 08:29:00 GMT

接着来。
2.过滤器的配置：
我们已经配置了那些过滤器了，但是要跟spring context中的对象对应，于是乎，做了如下配置：
          class="org.springframework.security.web.context.SecurityContextPersistenceFilter">

          class="org.springframework.security.web.authentication.logout.LogoutFilter" >

          class="org.springframework.security.web.authentication.www.BasicAuthenticationFilter">



          class="org.springframework.security.web.savedrequest.RequestCacheAwareFilter">

          class="org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter">

          class="org.springframework.security.web.authentication.AnonymousAuthenticationFilter">



          class="org.springframework.security.web.session.SessionManagementFilter">

          class="org.springframework.security.web.access.ExceptionTranslationFilter">


          class="org.springframework.security.web.access.intercept.FilterSecurityInterceptor">




          class="org.springframework.security.web.authentication.logout.SecurityContextLogoutHandler">

          class="org.springframework.security.core.userdetails.memory.UserAttribute">







          class="org.springframework.security.core.authority.GrantedAuthorityImpl">

          class="org.springframework.security.web.context.HttpSessionSecurityContextRepository">

          class="org.springframework.security.access.vote.AffirmativeBased">






          class="com.saveworld.authentication.web.access.expression.MyWebExpressionVoter">

          class="com.saveworld.authentication.web.access.intercept.MyFilterInvocationSecurityMetadataSource">

ref="expressionHandler" />

class="org.springframework.security.web.util.AntUrlPathMatcher" >

          class="org.springframework.security.web.access.expression.DefaultWebSecurityExpressionHandler">

这里做几点说明：
   (1) 数据库中的权限相关的表：
            ROLES
      AUTHORITIES
            USER_AUTHS
            ROLE_AUTHS
            USERS
       这里的表结构还不是最终的，所以就不发上来误导兄弟姐妹们了。
       关键是看我们如何加载这些持久化的东西。
       这个就要看看filterSecurityInterceptor了，它里面使用了一个securityMetadataSource，本地的securityMetadataSource实现代码：
      public class MyFilterInvocationSecurityMetadataSource extends DefaultFilterInvocationSecurityMetadataSource{
    private final static Log logger = LogFactory.getLog(ExpressionBasedFilterInvocationSecurityMetadataSource.class);
    private DataSource datasource;

    public MyFilterInvocationSecurityMetadataSource(UrlMatcher urlMatcher,
                                                    DataSource datasource,
                                                    WebSecurityExpressionHandler expressionHandler) {
        super(urlMatcher, processMap(initializeFromDb(datasource,null),expressionHandler.getExpressionParser()));
    }

    //This method is usefulless for now!
    //Because this method is used for parsing the expression kind
    private static LinkedHashMap> processMap(
            LinkedHashMap> requestMap, ExpressionParser parser) {
        Assert.notNull(parser, "SecurityExpressionHandler returned a null parser object");

        LinkedHashMap> requestToExpressionAttributesMap =
            new LinkedHashMap>(requestMap);

        for (Map.Entry> entry : requestMap.entrySet()) {
            RequestKey request = entry.getKey();
            Assert.isTrue(entry.getValue().size() == 1, "Expected a single expression attribute for " + request);
            ArrayList attributes = new ArrayList(1);
            String expression = entry.getValue().toArray(new ConfigAttribute[1])[0].getAttribute();
            logger.debug("Adding web access control expression '" + expression + "', for " + request);
            try {
                //Replacing WebExpressionConfigAttribute with MyWebExpressionConfigAttribute
                //which is defined locally!
                attributes.add(new MyWebExpressionConfigAttribute(parser.parseExpression(expression)));
            } catch (ParseException e) {
                throw new IllegalArgumentException("Failed to parse expression '" + expression + "'");
            }

            requestToExpressionAttributesMap.put(request, attributes);
        }

        return requestToExpressionAttributesMap;
    }

    private static LinkedHashMap> initializeFromDb(DataSource datasource,LinkedHashMap> configMap){
        LinkedHashMap> result =
            new LinkedHashMap>();
        Connection conn = null;
        Statement stmt = null;
        ResultSet rs   = null;
        try {
            conn = datasource.getConnection();
            stmt = conn.createStatement();
            StringBuilder sql = new StringBuilder("SELECT b.AUTHORITYPATTERN ,'hasRole('||chr(39)||a.ROLENAME||chr(39)||')' rolename ")
                                             .append(" FROM ROLES a,AUTHORITIES b,ROLE_AUTHS c ")
                                             .append(" WHERE a.rolename = c.rolename AND b.authorityname = c.authorityname");

            rs = stmt.executeQuery(sql.toString());
            String roles = "";
            RequestKey key = null;
            List value = null;
            while(rs != null && rs.next()){
                key = new RequestKey(rs.getString(1));
                roles = rs.getString(2);
                String[] roleArray = roles.split(",|\\s+|;");
                value = new ArrayList();
                for(String role : roleArray){
                    ConfigAttribute config = new SecurityConfig(role);
                    value.add(config);
                }
                result.put(key, value);
            }
            //just for test
        } catch (SQLException e) {
            e.printStackTrace();
        } finally{
            try{
                rs.close();
                stmt.close();
                conn.close();
            }catch(SQLException e){
                e.printStackTrace();
            }
        }
        return result;
    }



    public boolean supports(Class clazz) {
        return FilterInvocation.class.isAssignableFrom(clazz);
    }

    public DataSource getDatasource() {
        return datasource;
    }

    public void setDatasource(DataSource datasource) {
        this.datasource = datasource;
    }
}
(2) expressionHandler:
     这个东西要单独说说，我这里用的是表达式来检测用户角色的，所以，我用org.springframework.security.web.access.expression.DefaultWebSecurityExpressionHandler来处理了，还有其他的方式，就是直接用角色进行判断，那样会更好，这里就不描述了！

taochen 2010-01-25 16:29 发表评论

SpringSecurity使用记录（六）-- 本地配置一

taochen — Mon, 25 Jan 2010 07:56:00 GMT

按照SpringSecurity的文档，我们可以使用namespace的配置方式（前篇中已经说明）。
但是，我们这里的需求有点蹊跷，就是通过spring context进行权限配置太不方便，你想想能让人家客户通过spring xml来配置权限吗？不能，坚决不能！所以，我就单步跟踪获取里面的东西（这种方法比直接看代码快点，而且可以知道里面的逻辑结构！）
那就开始吧：
1.配置FilterChainProxy：
SpringSecurity的验证过程是通过一系列的filter来实现的。
这种chain的设计模式比较经典，可以说相当经典！
看看代码实现：
上篇中说过，默认的配置要求springSecurityFilterChain，那这个springSecurityFilterChain是怎么来用的呢？
public class DelegatingFilterProxy extends GenericFilterBean {
... ... ...
protected void initFilterBean() throws ServletException {
        // If no target bean name specified, use filter name.
        if (this.targetBeanName == null) {
            this.targetBeanName = getFilterName();
        }

        // Fetch Spring root application context and initialize the delegate early,
        // if possible. If the root application context will be started after this
        // filter proxy, we'll have to resort to lazy initialization.
        synchronized (this.delegateMonitor) {
            WebApplicationContext wac = findWebApplicationContext();
            if (wac != null) {
                this.delegate = initDelegate(wac);
            }
        }
    }
.....
}
不用说，你会猜到我们没有配置过targetBeanName这个属性，所以，就有了this.targetBeanName = getFilterName();这样的话就会配置FilterChainProxy了，因为FilterChainProxy在springContext中id是springSecurityFilterChain，所以我们要通过自己的数据库方式配置的话，就要琢磨这个FilterChainProxy了！
所以，首先做点这样的配置吧：

这个里面配置的id为myFilterChain，所以要在web.xml里面做相应配置：

myFilterChain

org.springframework.web.filter.DelegatingFilterProxy

myFilterChain

而且，尤为重要的是要配置上这些过滤器：
filter-chain pattern="/**" filters="securityContextPersistenceFilter,logoutFilter,
                                             myUsernamePasswordAuthenticationFilter,
                                             basicAuthenticationFilter,
                                             requestCacheAwareFilter,
                                             securityContextHolderAwareRequestFilter,
                                             anonymousAuthenticationFilter,
                                             sessionManagementFilter,
                                             exceptionTranslationFilter,
                                             filterSecurityInterceptor"
针对这些过滤器的用途，在spring security的文档中有详细描述，这里不多说了，在文档中的具体位置是7.2 FilterChainProxy，看看这一章就会有感觉了，不过绝知此事要躬行啊！
完成这些配置之后，我们就算是把入口给搭建好了！
鉴于文档篇幅，换到下篇接着说。

taochen 2010-01-25 15:56 发表评论

SpringSecurity使用记录（五）-- 配置

taochen — Tue, 19 Jan 2010 06:19:00 GMT

研究了好长时间，不知道从哪里下手。新的版本，很多东西在网上找不到，只能看他们的文档，当然这些文档相当不错，就看是否耐心的研究了！总是有急躁的心理作祟，不能专心研读，却处处碰壁，效率上反而未达预期效果！
终于，在无数次的沮丧下，稍微看到了点光亮！前面的文章太过皮毛，接下来的一些，希望能更加实际的，更加深入的分析每一个过程！

一直通过默认配置进行设置：
namespace(是security 3.0,网上也看到一些兄弟描述的是3.0，但是总是不符合我这里的namespace配置):
           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-3.0.xsd
               http://www.springframework.org/schema/security
               http://www.springframework.org/schema/security/spring-security-3.0.xsd">
按照默认配置的http（这是用来根据namespace设置的基本的security过滤器chain）：
auto-config=true时，就相当于

也就是使用了默认的过滤器。
我最开始的想法是能够把本地的login信息（不是调用spring security的login方法），传入到spring security的验证过滤器里面。
这里有一个比较关键的问题，就是封装他们的过滤器（或者仅仅是知道他们到底是哪些过滤器在起作用）：
表1

Alias	Filter Class	Namespace Element or Attribute
CHANNEL_FILTER	`ChannelProcessingFilter`	`http/intercept-url@requires-channel`
CONCURRENT_SESSION_FILTER	`ConcurrentSessionFilter`	`session-management/concurrency-control`
SECURITY_CONTEXT_FILTER	`SecurityContextPersistenceFilter`	`http`
LOGOUT_FILTER	`LogoutFilter`	`http/logout`
X509_FILTER	`X509AuthenticationFilter`	`http/x509`
PRE_AUTH_FILTER	`AstractPreAuthenticatedProcessingFilter` Subclasses	N/A
CAS_FILTER	`CasAuthenticationFilter`	N/A
FORM_LOGIN_FILTER	`UsernamePasswordAuthenticationFilter`	`http/form-login`
BASIC_AUTH_FILTER	`BasicAuthenticationFilter`	`http/http-basic`
SERVLET_API_SUPPORT_FILTER	`SecurityContextHolderAwareFilter`	`http/@servlet-api-provision`
REMEMBER_ME_FILTER	`RememberMeAuthenticationFilter`	`http/remember-me`
ANONYMOUS_FILTER	`AnonymousAuthenticationFilter`	`http/anonymous`
SESSION_MANAGEMENT_FILTER	`SessionManagementFilter`	`session-management`
EXCEPTION_TRANSLATION_FILTER	`ExceptionTranslationFilter`	`http`
FILTER_SECURITY_INTERCEPTOR	`FilterSecurityInterceptor`	`http`
SWITCH_USER_FILTER	`SwitchUserFilter`	N/A

（最开始看的时候，把这个表格忽略了，现在看来这些就是我们想要的！）
我们的验证过程，就是按照这样的顺序进行的。自上而下进行。

如果我们要自己定制相应的验证处理方法（在过滤器里面），我们就可以对照上面的过滤器，覆盖相应的接口方法。
根据我的处理过程，主要是用户名密码的验证过程，我大体描述一下自己的配置和处理过程：
1.配置namespace的标签:

这里的问题是，要定制自己的过滤器，就要通过，然后对照表1 中指定的position,覆盖默认的filter。
2.我的form-login filter配置（这些配置都是在application-security.xml文件中）为：
      class="com.saveworld.authentication.filters.MyUsernamePasswordAuthenticationFilter">






NOTE：
在这里有个问题就是： filter position conflicts!
如果使用这样的配置

自定义的filter对应的position是FORM_LOGIN_FILTER
但是因为使用了auto-config='true'，所以默认有，which is on the position FORM_LOGIN_FILTER!
这时就会出现position conflicts问题了。当然，如果你没有设置auto-config='true'，但是却自己设置了，呵呵，这个情况就是自己大意了，还是有了position conflicts的异常，所以，好好看看上面的表格是相当必要的，看清楚每个position默认都对应那些namespace，都是对应的哪些filter！

接着：
我的类MyUsernamePasswordAuthenticationFilter实现（我的说明方式就按照哪里需要，哪里加入的方式了）：
package com.saveworld.authentication.filters;

import java.io.IOException;

import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;

import org.springframework.security.authentication.AuthenticationServiceException;
import org.springframework.security.authentication.UsernamePasswordAuthenticationToken;
import org.springframework.security.authentication.event.InteractiveAuthenticationSuccessEvent;
import org.springframework.security.core.Authentication;
import org.springframework.security.core.AuthenticationException;
import org.springframework.security.core.context.SecurityContextHolder;
import org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter;
import org.springframework.security.web.authentication.AuthenticationFailureHandler;
import org.springframework.security.web.authentication.AuthenticationSuccessHandler;
import org.springframework.security.web.authentication.NullRememberMeServices;
import org.springframework.security.web.authentication.RememberMeServices;
import org.springframework.security.web.authentication.SavedRequestAwareAuthenticationSuccessHandler;
import org.springframework.security.web.authentication.SimpleUrlAuthenticationFailureHandler;
import org.springframework.security.web.util.TextEscapeUtils;
import org.springframework.util.Assert;

import com.saveworld.authentication.handlers.MySavedRequestAwareAuthenticationSuccessHandler;
import com.saveworld.authentication.handlers.MySimpleUrlAuthenticationFailureHandler;

public class MyUsernamePasswordAuthenticationFilter extends AbstractAuthenticationProcessingFilter{
    //~ Static fields/initializers =====================================================================================

    public static final String SPRING_SECURITY_FORM_USERNAME_KEY = "username";
    public static final String SPRING_SECURITY_FORM_PASSWORD_KEY = "password";
    public static final String SPRING_SECURITY_LAST_USERNAME_KEY = "SPRING_SECURITY_LAST_USERNAME";

    private String usernameParameter = SPRING_SECURITY_FORM_USERNAME_KEY;
    private String passwordParameter = SPRING_SECURITY_FORM_PASSWORD_KEY;
    private boolean postOnly = true;

    private boolean allowSessionCreation = true;

    private String defaultTargetUrl = "/";
    private String defaultFailureUrl = "/login.jsp";

    private AuthenticationSuccessHandler successHandler = null;
    private AuthenticationFailureHandler failureHandler = null;


    private RememberMeServices rememberMeServices = null;

    //~ Constructors ===================================================================================================

    public MyUsernamePasswordAuthenticationFilter() {
        //初始化
        super("/j_spring_security_check");
        this.rememberMeServices = (super.getRememberMeServices() == null)
                                    ? new NullRememberMeServices():super.getRememberMeServices();

    }

    //~ Methods ========================================================================================================

    public Authentication attemptAuthentication(HttpServletRequest request, HttpServletResponse response) throws AuthenticationException {
        if (postOnly && !request.getMethod().equals("POST")) {
            throw new AuthenticationServiceException("Authentication method not supported: " + request.getMethod());
        }

        String username = obtainUsername(request);
        String password = obtainPassword(request);

        if (username == null) {
            username = "";
        }

        if (password == null) {
            password = "";
        }

        username = username.trim();

        UsernamePasswordAuthenticationToken authRequest = new UsernamePasswordAuthenticationToken(username, password);

        // Place the last username attempted into HttpSession for views
        HttpSession session = request.getSession(false);

        if (session != null || getAllowSessionCreation()) {
            request.getSession().setAttribute(SPRING_SECURITY_LAST_USERNAME_KEY, TextEscapeUtils.escapeEntities(username));
        }

        // Allow subclasses to set the "details" property
        setDetails(request, authRequest);

        return this.getAuthenticationManager().authenticate(authRequest);
    }



    public void successfulAuthentication(HttpServletRequest request, HttpServletResponse response,
            Authentication authResult) throws IOException, ServletException {

        if (logger.isDebugEnabled()) {
            logger.debug("Authentication success. Updating SecurityContextHolder to contain: " + authResult);
        }

        SecurityContextHolder.getContext().setAuthentication(authResult);

        rememberMeServices.loginSuccess(request, response, authResult);

        // Fire event
        if (this.eventPublisher != null) {
            eventPublisher.publishEvent(new InteractiveAuthenticationSuccessEvent(authResult, this.getClass()));
        }
        if(successHandler == null){
            successHandler = new MySavedRequestAwareAuthenticationSuccessHandler(getDefaultTargetUrl());
        }
        successHandler.onAuthenticationSuccess(request, response, authResult);
    }

    public void unsuccessfulAuthentication(HttpServletRequest request, HttpServletResponse response,
            AuthenticationException failed) throws IOException, ServletException {
        SecurityContextHolder.clearContext();

        if(failureHandler == null){
            failureHandler = new MySimpleUrlAuthenticationFailureHandler(getDefaultFailureUrl());
        }

        if (logger.isDebugEnabled()) {
            logger.debug("Authentication request failed: " + failed.toString());
            logger.debug("Updated SecurityContextHolder to contain null Authentication");
            logger.debug("Delegating to authentication failure handler" + failureHandler);
        }

        HttpSession session = request.getSession(false);

        if (session != null || allowSessionCreation) {
            request.getSession().setAttribute(SPRING_SECURITY_LAST_EXCEPTION_KEY, failed);
        }

        rememberMeServices.loginFail(request, response);

        failureHandler.onAuthenticationFailure(request, response, failed);
    }


    /**
     * Enables subclasses to override the composition of the password, such as by including additional values
     * and a separator.

This might be used for example if a postcode/zipcode was required in addition to the
* password. A delimiter such as a pipe (|) should be used to separate the password and extended value(s). The
* AuthenticationDao will need to generate the expected password in a corresponding manner.

     *
     * @param request so that request attributes can be retrieved
     *
     * @return the password that will be presented in the Authentication request token to the
     *         AuthenticationManager
     */
    protected String obtainPassword(HttpServletRequest request) {
        return request.getParameter(passwordParameter);
    }

    /**
     * Enables subclasses to override the composition of the username, such as by including additional values
     * and a separator.
     *
     * @param request so that request attributes can be retrieved
     *
     * @return the username that will be presented in the Authentication request token to the
     *         AuthenticationManager
     */
    protected String obtainUsername(HttpServletRequest request) {
        return request.getParameter(usernameParameter);
    }

    /**
     * Provided so that subclasses may configure what is put into the authentication request's details
     * property.
     *
     * @param request that an authentication request is being created for
     * @param authRequest the authentication request object that should have its details set
     */
    protected void setDetails(HttpServletRequest request, UsernamePasswordAuthenticationToken authRequest) {
        authRequest.setDetails(authenticationDetailsSource.buildDetails(request));
    }

    /**
     * Sets the parameter name which will be used to obtain the username from the login request.
     *
     * @param usernameParameter the parameter name. Defaults to "j_username".
     */
    public void setUsernameParameter(String usernameParameter) {
        Assert.hasText(usernameParameter, "Username parameter must not be empty or null");
        this.usernameParameter = usernameParameter;
    }

    /**
     * Sets the parameter name which will be used to obtain the password from the login request..
     *
     * @param passwordParameter the parameter name. Defaults to "j_password".
     */
    public void setPasswordParameter(String passwordParameter) {
        Assert.hasText(passwordParameter, "Password parameter must not be empty or null");
        this.passwordParameter = passwordParameter;
    }

    /**
     * Defines whether only HTTP POST requests will be allowed by this filter.
     * If set to true, and an authentication request is received which is not a POST request, an exception will
     * be raised immediately and authentication will not be attempted. The unsuccessfulAuthentication() method
     * will be called as if handling a failed authentication.
     *

     * Defaults to true but may be overridden by subclasses.
     */
    public void setPostOnly(boolean postOnly) {
        this.postOnly = postOnly;
    }

    public final String getUsernameParameter() {
        return usernameParameter;
    }

    public final String getPasswordParameter() {
        return passwordParameter;
    }

    public String getDefaultTargetUrl() {
        return defaultTargetUrl;
    }

    public void setDefaultTargetUrl(String defaultTargetUrl) {
        this.defaultTargetUrl = defaultTargetUrl;
    }

    public String getDefaultFailureUrl() {
        return defaultFailureUrl;
    }

    public void setDefaultFailureUrl(String defaultFailureUrl) {
        this.defaultFailureUrl = defaultFailureUrl;
    }


}

这里要关注的就是几个字段：


这两个字段是指定验证成功或失败后转向的页面，这里要注意是以“/”开头，否则在AbstractAuthenticationTargetUrlRequestHandler中调用setDefaultTargetUrl方法时会抛出"defaultTarget must start with '/' or with 'http(s)'"的异常！
默认情况下，FORM_LOGIN_FILTER对应的target url和failure url都是通过中的default-target-url,authentication-failure-url指定，也可以通过指定authentication-success-handler-ref和authentication-failure-handler-ref来实现认证成功和失败之后的处理方式.在我的filter中，是自定义了两个handler分别对应成功的和失败的验证。

3.用户信息获取和验证：



这个指定的authentication-manager是使用默认的ProviderManager，这个manager是在哪里使用的呢？
看看MyUsernamePasswordAuthenticationFilter中的attemptAuthentication方法的最后一行，这里是获取指定的authentication-manager。getAuthenticationManager是从父类AbstractAuthenticationProcessingFilter继承过来的。所以，我们的中就指定了一个别名authenticationManager，在myfilter中设置属性的引用，然后我们就可以通过Provider引用我们自己的用户信息验证service了（eg:用户信息获取和验证）！这里实际是使用了Method Template模式（AbstractAuthenticationManager中设定模板函数doAuthentication，ProviderManager中做了实现）。
这里难免要说明一下，我们的Service是如何被调用的，我们做了配置
指定了我们的UserDetailsService，类实现(为了测试和理解，The easier the better!)：
package com.saveworld.userdetails;

import java.util.ArrayList;
import java.util.HashMap;
import java.util.List;

import org.springframework.dao.DataAccessException;
import org.springframework.security.core.GrantedAuthority;
import org.springframework.security.core.authority.GrantedAuthorityImpl;
import org.springframework.security.core.userdetails.User;
import org.springframework.security.core.userdetails.UserDetails;
import org.springframework.security.core.userdetails.UserDetailsService;
import org.springframework.security.core.userdetails.UsernameNotFoundException;

public class MyUserDetailsService implements UserDetailsService{

    private HashMap userDetails = new HashMap();
    private HashMap> userAuthorities = new HashMap>();

    public MyUserDetailsService(){
        //Make up a user named 'rod' with 'rod' as his password!
        //
        String username = "rod";
        String password = "1";
        boolean enabled = true;
        //purview for rod
        GrantedAuthority specAuth = new GrantedAuthorityImpl("ROLE_MY");
        List rodsAuthsList = new ArrayList();
        rodsAuthsList.add(specAuth);
//        userAuthorities.put("rod", rodsAuthsList);
        userDetails.put("rod", new User(username, password, enabled, true, true, true, rodsAuthsList));
    }


    public UserDetails loadUserByUsername(String username)
            throws UsernameNotFoundException, DataAccessException {
        System.out.println("验证从此地过了一遭");
        return userDetails.get(username);
    }

}
通过DaoAuthenticationProvider中的userDetailsService关联我们的UserDetailsService（不得不提的是，AbstractUserDetailsAuthenticationProvider中有设定了模板函数retrieveUser，DaoAuthenticationProvider进行了实现，通过retrieveUser方法调用UserDetailsService.loadUserByUsername，然后在AbstractUserDetailsAuthenticationProvider.authenticate方法进行验证）。
接下来就是看验证的结果了，是否成功，进入filter chain中。
这一切就这么有条不紊的进行了！呵呵，总算是有点成果了！有了一点点感性的认识了！上面的描述中难免会有些混乱，但是尽量是哪里需要，哪里就做说明！

下篇中说明entrypoint的用处吧！

taochen 2010-01-19 14:19 发表评论

SpringSecurity使用记录（二）--核心分析篇

taochen — Fri, 25 Dec 2009 07:53:00 GMT

不得不再感叹一下，策略模式在SpringSecurity中用的地方太多了！

? SecurityContextHolder, to provide access to the SecurityContext.
? SecurityContext, to hold the Authentication and possibly request-specific security
information.
? Authentication, to represent the principal in a Spring Security-specific manner.
? GrantedAuthority, to reflect the application-wide permissions granted to a principal.
? UserDetails, to provide the necessary information to build an Authentication object from your
application's DAOs or other source source of security data.
? UserDetailsService, to create a UserDetails when passed in a String-based username
(or certificate ID or the like).
（以上是从文档里面抄出来的！）
这就是权限的核心了！！（持续修改中。。。。。。）

taochen 2009-12-25 15:53 发表评论

SpringSecurity使用记录（一）

taochen — Thu, 24 Dec 2009 12:05:00 GMT

第一次配置和使用SpringSecurity，总是要碰很多次墙！
先说说个人理解的它里面比较有意义的架构。
里面有好多设计模式的影子：策略模式，代理模式，工厂模式，链条模式=====，看到这些模式（除了工厂或单例）心里总是会有些兴奋，总算是看到了模式的真正练兵场！跟兄弟们好好分享一下!(才看了一天！有不对之处，还望各位斧正！)
策略模式（Strategy Pattern）:
主要说一下session相关的这个策略模式，以SessionAuthenticationStrategy接口的策略划分，根据我们的session安全策略，指定不同的策略，现在看是这种布局：

顶层接口	SessionAuthenticationStrategy
具体实现	SessionFixationProtectionStrategy （直接默认实现）	NullAuthenticatedSessionStrategy （空实现）
二级实现	ConcurrentSessionControlStrategy

画图比较麻烦，各位还是凑合着看吧！说明一下：顶层接口被下面“具体实现”两个类实现，而“二级实现”实现SessionFixationProtectionStrategy。具体采用哪种策略要看我们的配置了！
代理模式（Proxy）：
很明显的代理类，DelegatingFilterProxy和FilterChainProxy，这两个类看着心里都痒痒的，呵呵，平常总是看代理模式呀什么的，即时看着例子也不踏实，现在看到这两个东西，心里突然有种平静的激动！
这两个代理类以FilterChainProxy为例说明一下吧，FilterChainProxy代理了权限验证Filters的工作，通过它来访问整个过滤器串里面的过滤器。
Chain模式：这个也应该以FilterChainProxy这个类入口来分析，呵呵，有兴趣的各位就通过这个来看看吧！

taochen 2009-12-24 20:05 发表评论