总:

用户通过浏览器发送URL地址,由FilterSecurityInterceptor判断是否具有相应的访问权限。
对于用户请求的方法权限,例如注解@PreAuthorize("hasRole('ADMIN')"),由MethodSecurityInterceptor判断
两个拦截器都继承了AbstractSecurityInterceptor

  1. /*
  2. * Copyright 2004, 2005, 2006 Acegi Technology Pty Limited
  3. *
  4. * Licensed under the Apache License, Version 2.0 (the "License");
  5. * you may not use this file except in compliance with the License.
  6. * You may obtain a copy of the License at
  7. *
  8. * http://www.apache.org/licenses/LICENSE-2.0
  9. *
  10. * Unless required by applicable law or agreed to in writing, software
  11. * distributed under the License is distributed on an "AS IS" BASIS,
  12. * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  13. * See the License for the specific language governing permissions and
  14. * limitations under the License.
  15. */
  16. package org.springframework.security.web.access.intercept;
  17. import java.io.IOException;
  18. import javax.servlet.Filter;
  19. import javax.servlet.FilterChain;
  20. import javax.servlet.FilterConfig;
  21. import javax.servlet.ServletException;
  22. import javax.servlet.ServletRequest;
  23. import javax.servlet.ServletResponse;
  24. import org.springframework.security.access.SecurityMetadataSource;
  25. import org.springframework.security.access.intercept.AbstractSecurityInterceptor;
  26. import org.springframework.security.access.intercept.InterceptorStatusToken;
  27. import org.springframework.security.web.FilterInvocation;
  28. /**
  29. * Performs security handling of HTTP resources via a filter implementation.
  30. * 通过筛选器实现对HTTP资源的安全处理。
  31. * <p>
  32. * The <code>SecurityMetadataSource</code> required by this security interceptor is of
  33. * type {@link FilterInvocationSecurityMetadataSource}.
  34. * <p>
  35. *安全拦截器所需的SecurityMetadataSource类型是FilterInvocationSecurityMetadataSource
  36. *
  37. * Refer to {@link AbstractSecurityInterceptor} for details on the workflow.
  38. * </p>
  39. *
  40. * @author Ben Alex
  41. * @author Rob Winch
  42. */
  43. public class FilterSecurityInterceptor extends AbstractSecurityInterceptor implements
  44. Filter {
  45. // ~ Static fields/initializers
  46. // =====================================================================================
  47. private static final String FILTER_APPLIED = "__spring_security_filterSecurityInterceptor_filterApplied";
  48. // ~ Instance fields
  49. // ================================================================================================
  50. /**
  51. *securityMetadataSource 中包含了一个HashMap,map中保存了用户请求的Http.Method和相应的URL地址
  52. *例如在Spring boot中,可能是如下的配置,参考图1
  53. *securityMetadataSource中的内容,参考图2
  54. */
  55. private FilterInvocationSecurityMetadataSource securityMetadataSource;
  56. private boolean observeOncePerRequest = true;
  57. // ~ Methods
  58. // ========================================================================================================
  59. /**
  60. * Not used (we rely on IoC container lifecycle services instead)
  61. *
  62. * @param arg0 ignored
  63. *
  64. * @throws ServletException never thrown
  65. */
  66. public void init(FilterConfig arg0) throws ServletException {
  67. }
  68. /**
  69. * Not used (we rely on IoC container lifecycle services instead)
  70. */
  71. public void destroy() {
  72. }
  73. /**
  74. * Method that is actually called by the filter chain. Simply delegates to the
  75. * {@link #invoke(FilterInvocation)} method.
  76. *
  77. * @param request the servlet request
  78. * @param response the servlet response
  79. * @param chain the filter chain
  80. *
  81. * @throws IOException if the filter chain fails
  82. * @throws ServletException if the filter chain fails
  83. *
  84. *
  85. *通过责任链式调用,执行doFilter方法
  86. *FilterInvocation中保存了filter相关的信息,比如request,response,chain
  87. *通过invoke方法处理具体的url过滤
  88. */
  89. public void doFilter(ServletRequest request, ServletResponse response,
  90. FilterChain chain) throws IOException, ServletException {
  91. FilterInvocation fi = new FilterInvocation(request, response, chain);
  92. invoke(fi);
  93. }
  94. public FilterInvocationSecurityMetadataSource getSecurityMetadataSource() {
  95. return this.securityMetadataSource;
  96. }
  97. public SecurityMetadataSource obtainSecurityMetadataSource() {
  98. return this.securityMetadataSource;
  99. }
  100. public void setSecurityMetadataSource(FilterInvocationSecurityMetadataSource newSource) {
  101. this.securityMetadataSource = newSource;
  102. }
  103. public Class<?> getSecureObjectClass() {
  104. return FilterInvocation.class;
  105. }
  106. public void invoke(FilterInvocation fi) throws IOException, ServletException {
  107. //获取当前http请求的地址,比如说“/login”
  108. if ((fi.getRequest() != null)
  109. && (fi.getRequest().getAttribute(FILTER_APPLIED) != null)
  110. && observeOncePerRequest) {
  111. // filter already applied to this request and user wants us to observe
  112. // once-per-request handling, so don't re-do security checking
  113. fi.getChain().doFilter(fi.getRequest(), fi.getResponse());
  114. }
  115. else {
  116. // first time this request being called, so perform security checking
  117. if (fi.getRequest() != null) {
  118. fi.getRequest().setAttribute(FILTER_APPLIED, Boolean.TRUE);
  119. }
  120. //这里做主要URL比对,将当前URL与securityMetadataSource(我们自己配置)中的URL过滤条件进行比对
  121. //首先判断当前URL是permit的还是需要验证的
  122. //若需要验证,尝试加载保存在SecurityContextHolder.getContext()中的已登录信息
  123. //调用AbstractSecurityInterceptor中的AccessDecisionManager对象的decide方法
  124. //如果对于配置中需要登录才可访问的URL,已经查找到登录信息,则执行下一个Filter
  125. InterceptorStatusToken token = super.beforeInvocation(fi);
  126. try {
  127. fi.getChain().doFilter(fi.getRequest(), fi.getResponse());
  128. }
  129. finally {
  130. super.finallyInvocation(token);
  131. }
  132. super.afterInvocation(token, null);
  133. }
  134. }
  135. /**
  136. * Indicates whether once-per-request handling will be observed. By default this is
  137. * <code>true</code>, meaning the <code>FilterSecurityInterceptor</code> will only
  138. * execute once-per-request. Sometimes users may wish it to execute more than once per
  139. * request, such as when JSP forwards are being used and filter security is desired on
  140. * each included fragment of the HTTP request.
  141. *
  142. * @return <code>true</code> (the default) if once-per-request is honoured, otherwise
  143. * <code>false</code> if <code>FilterSecurityInterceptor</code> will enforce
  144. * authorizations for each and every fragment of the HTTP request.
  145. */
  146. public boolean isObserveOncePerRequest() {
  147. return observeOncePerRequest;
  148. }
  149. public void setObserveOncePerRequest(boolean observeOncePerRequest) {
  150. this.observeOncePerRequest = observeOncePerRequest;
  151. }
  152. }

Spring security用户URL权限之FilterSecurityInterceptor的更多相关文章

  1. Spring Security 动态url权限控制(三)

    一.前言 本篇文章将讲述Spring Security 动态分配url权限,未登录权限控制,登录过后根据登录用户角色授予访问url权限 基本环境 spring-boot 2.1.8 mybatis-p ...

  2. Spring Security实现RBAC权限管理

    Spring Security实现RBAC权限管理 一.简介 在企业应用中,认证和授权是非常重要的一部分内容,业界最出名的两个框架就是大名鼎鼎的 Shiro和Spring Security.由于Spr ...

  3. 登陆模块,这个是很重要的模块,有shiro和spring security专门的权限认证框架

    登陆模块,这个是很重要的模块,有shiro和spring security专门的权限认证框架

  4. Spring Security 基于URL的权限判断

    1.  FilterSecurityInterceptor 源码阅读 org.springframework.security.web.access.intercept.FilterSecurityI ...

  5. Spring security 用户,角色,权限,资源

    转自:http://blog.csdn.net/wybqq/article/details/52940194 关于Spring security对用户请求的处理过程 体现在这两个过程的体现. 关于用户 ...

  6. spring security 登录、权限管理配置

    登录流程 1)容器启动(MySecurityMetadataSource:loadResourceDefine加载系统资源与权限列表)  2)用户发出请求  3)过滤器拦截(MySecurityFil ...

  7. 别再让你的微服务裸奔了,基于 Spring Session & Spring Security 微服务权限控制

    微服务架构 网关:路由用户请求到指定服务,转发前端 Cookie 中包含的 Session 信息: 用户服务:用户登录认证(Authentication),用户授权(Authority),用户管理(R ...

  8. Spring Security 自定义 登陆 权限验证

    转载于:https://www.jianshu.com/p/6b8fb59b614b 项目简介 基于Spring Cloud 的项目,Spring Cloud是在Spring Boot上搭建的所以按照 ...

  9. 获取spring security用户相关信息

    在JSP中获得 使用spring security的标签库 在页面中引入标签 <%@ taglib prefix="sec" uri="http://www.spr ...

随机推荐

  1. 2019-1-17-一段能让-VisualStudio-炸掉的代码

    title author date CreateTime categories 一段能让 VisualStudio 炸掉的代码 lindexi 2019-01-17 09:55:29 +0800 20 ...

  2. OSI七层模型,作用及其对应的协议

    物理层(Physical Layer):利用传输介质为数据链路层提供物理连接,实现比特流的透明传输 数据链路层(Data Link Layer):负责建立和管理节点间的链路 网络层(Network L ...

  3. Function相关的小知识

      重载 相同函数名,不同参数列表的多个函数,在调用时可自动根据传入参数的不同,选择对应的函数执行.为什么使用重载:                   减轻API的名字,减轻调用者的负担.何时使用重 ...

  4. 【JZOJ4923】【NOIP2017提高组模拟12.17】巧克力狂欢

    题目描述 Alice和Bob有一棵树(无根.无向),在第i个点上有ai个巧克力.首先,两人个选择一个起点(不同的),获得点上的巧克力:接着两人轮流操作(Alice先),操作的定义是:在树上找一个两人都 ...

  5. 大数据技术之Hive

    第1章 Hive入门 1.1 什么是Hive Hive:由Facebook开源用于解决海量结构化日志的数据统计. Hive是基于Hadoop的一个数据仓库工具,可以将结构化的数据文件映射为一张表,并提 ...

  6. mac进行acm(C/C++)编程

    在windows下我们往往使用CB(CodeBlocksks)进行acm的编程,不用建立工程,可以直接编译并运行,然后弹出黑框框,sublime也是这样,只要MinGW搞好就行 在ubuntu下我也常 ...

  7. 两种RBAC权限控制模型详解

    序言 由于最近一直卡在权限控制这个坎上,原来设计的比较简单的权限控制思路已经无法满足比较复杂一些的场景,因此一直在探索一种在大部分场景下比较通用的权限模型. 首先,这里说明一下两种RBAC权限模型分别 ...

  8. IntelliJ IDEA 添加项目后编译显示包不存在的解决方案

    File -> Project Structure -> Modules 看看是否有多个项目,删掉无用的.或者调整一下项目,重新 Mark as 一下,指定成 Sources

  9. iOS开发 底层抛析运行循环—— RunLoop

    http://blog.csdn.net/zc639143029/article/details/50012527 一.RunLoop基本概念 概念:程序的运行循环,通俗的来说就是跑圈. 1. 基本作 ...

  10. 基于GD库的php验证码类(支持中英文字体、背景、干扰点线、扭曲…….)

    转自:http://www.blhere.com/1168.html 12345678910111213141516171819202122232425262728293031323334353637 ...