分享

Spring Security3.1 最新配置实例

 BlazerOfIT 2012-07-09

这几天学习了一下Spring Security3.1,从官网下载了Spring Security3.1版本进行练习,经过多次尝试才摸清了其中的一些原理。本人不才,希望能帮助大家。还有,这次我第二次写博客啊,文体不是很行。希望能让观看者不产生疲惫的感觉,我已经心满意足了。

一、数据库结构

先来看一下数据库结构,采用的是基于角色-资源-用户的权限管理设计。(MySql数据库)

为了节省篇章,只对比较重要的字段进行注释。

1.用户表Users

CREATE TABLE `users` (

-- 账号是否有限 1. 是 0.否
`enable` int(11) default NULL,
`password` varchar(255) default NULL,
`account` varchar(255) default NULL,
`id` int(11) NOT NULL auto_increment,
PRIMARY KEY (`id`)
)

2.角色表Roles

CREATE TABLE `roles` (
`enable` int(11) default NULL,
`name` varchar(255) default NULL,
`id` int(11) NOT NULL auto_increment,
PRIMARY KEY (`id`)
)

3 用户_角色表users_roles

CREATE TABLE `users_roles` (

--用户表的外键
`uid` int(11) default NULL,

--角色表的外键
`rid` int(11) default NULL,
`urId` int(11) NOT NULL auto_increment,
PRIMARY KEY (`urId`),
KEY `rid` (`rid`),
KEY `uid` (`uid`),
CONSTRAINT `users_roles_ibfk_1` FOREIGN KEY (`rid`) REFERENCES `roles` (`id`),
CONSTRAINT `users_roles_ibfk_2` FOREIGN KEY (`uid`) REFERENCES `users` (`id`)
)

4.资源表resources

CREATE TABLE `resources` (
`memo` varchar(255) default NULL,

-- 权限所对应的url地址
`url` varchar(255) default NULL,

--优先权
`priority` int(11) default NULL,

--类型
`type` int(11) default NULL,

--权限所对应的编码,例201代表发表文章
`name` varchar(255) default NULL,
`id` int(11) NOT NULL auto_increment,
PRIMARY KEY (`id`)
)

5.角色_资源表roles_resources

CREATE TABLE `roles_resources` (
`rsid` int(11) default NULL,
`rid` int(11) default NULL,
`rrId` int(11) NOT NULL auto_increment,
PRIMARY KEY (`rrId`),
KEY `rid` (`rid`),
KEY `roles_resources_ibfk_2` (`rsid`),
CONSTRAINT `roles_resources_ibfk_2` FOREIGN KEY (`rsid`) REFERENCES `resources` (`id`),
CONSTRAINT `roles_resources_ibfk_1` FOREIGN KEY (`rid`) REFERENCES `roles` (`id`)
)

二、系统配置

所需要的jar包,请自行到官网下载,我用的是Spring Security3.1.0.RC1版的。把dist下的除了源码件包导入就行了。还有那些零零碎的 数据库驱动啊,log4j.jar等等,我相信在用Spring Security之前,大家已经会的了。

1) web.xml

  1. <!-- Spring -->
  2. <context-param>
  3. <param-name>contextConfigLocation</param-name>
  4. <param-value>classpath:applicationContext.xml,classpath:applicationContext-security.xml</param-value>
  5. </context-param>
  6. <listener>
  7. <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
  8. </listener>
  9. <!-- 权限 -->
  10. <filter>
  11. <filter-name>springSecurityFilterChain</filter-name>
  12. <filter-class>
  13. org.springframework.web.filter.DelegatingFilterProxy
  14. </filter-class>
  15. </filter>
  16. <filter-mapping>
  17. <filter-name>springSecurityFilterChain</filter-name>
  18. <url-pattern>/*</url-pattern>
  19. </filter-mapping>

这里主要是配置了让容器启动的时候加载application-security.xml和Spring Security的权限过滤器代理,让其过滤所有的客服请求。

2)application-security.xml

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <beans:beans xmlns="http://www./schema/security"
  3. xmlns:beans="http://www./schema/beans"
  4. xmlns:xsi="http://www./2001/XMLSchema-instance"
  5. xsi:schemaLocation="http://www./schema/beans http://www./schema/beans/spring-beans-3.0.xsd
  6. http://www./schema/security http://www./schema/security/spring-security-3.1.xsd">
  7. <global-method-security pre-post-annotations="enabled" />
  8. <!-- 该路径下的资源不用过滤 -->
  9. <http pattern="/js/**" security="none"/>
  10. <http use-expressions="true" auto-config="true">
  11. <form-login />
  12. <logout/>
  13. <!-- 实现免登陆验证 -->
  14. <remember-me />
  15. <session-management invalid-session-url="/timeout.jsp">
  16. <concurrency-control max-sessions="10" error-if-maximum-exceeded="true" />
  17. </session-management>
  18. <custom-filter ref="myFilter" before="FILTER_SECURITY_INTERCEPTOR"/>
  19. </http>
  20. <!-- 配置过滤器 -->
  21. <beans:bean id="myFilter" class="com.huaxin.security.MySecurityFilter">
  22. <!-- 用户拥有的权限 -->
  23. <beans:property name="authenticationManager" ref="myAuthenticationManager" />
  24. <!-- 用户是否拥有所请求资源的权限 -->
  25. <beans:property name="accessDecisionManager" ref="myAccessDecisionManager" />
  26. <!-- 资源与权限对应关系 -->
  27. <beans:property name="securityMetadataSource" ref="mySecurityMetadataSource" />
  28. </beans:bean>
  29. <!-- 实现了UserDetailsService的Bean -->
  30. <authentication-manager alias="myAuthenticationManager">
  31. <authentication-provider user-service-ref="myUserDetailServiceImpl" />
  32. </authentication-manager>
  33. <beans:bean id="myAccessDecisionManager" class="com.huaxin.security.MyAccessDecisionManager"></beans:bean>
  34. <beans:bean id="mySecurityMetadataSource" class="com.huaxin.security.MySecurityMetadataSource">
  35. <beans:constructor-arg name="resourcesDao" ref="resourcesDao"></beans:constructor-arg>
  36. </beans:bean>
  37. <beans:bean id="myUserDetailServiceImpl" class="com.huaxin.security.MyUserDetailServiceImpl">
  38. <beans:property name="usersDao" ref="usersDao"></beans:property>
  39. </beans:bean>
  40. </beans:beans>

我们在第二个http标签下配置一个我们自定义的继承了org.springframework.security.access.intercept.AbstractSecurityInterceptor的Filter,并注入其

必须的3个组件authenticationManager、accessDecisionManager和securityMetadataSource。其作用上面已经注释了。

<custom-filter ref="myFilter" before="FILTER_SECURITY_INTERCEPTOR"/> 这里的FILTER_SECURITY_INTERCEPTOR是Spring Security默认的Filter,

我们自定义的Filter必须在它之前,过滤客服请求。接下来看下我们最主要的myFilter吧。

3)myFilter

(1) MySecurityFilter.java 过滤用户请求

  1. public class MySecurityFilter extends AbstractSecurityInterceptor implements Filter {
  2. //与applicationContext-security.xml里的myFilter的属性securityMetadataSource对应,
  3. //其他的两个组件,已经在AbstractSecurityInterceptor定义
  4. private FilterInvocationSecurityMetadataSource securityMetadataSource;
  5. @Override
  6. public SecurityMetadataSource obtainSecurityMetadataSource() {
  7. return this.securityMetadataSource;
  8. }
  9. public void doFilter(ServletRequest request, ServletResponse response,
  10. FilterChain chain) throws IOException, ServletException {
  11. FilterInvocation fi = new FilterInvocation(request, response, chain);
  12. invoke(fi);
  13. }
  14. private void invoke(FilterInvocation fi) throws IOException, ServletException {
  15. // object为FilterInvocation对象
  16. //super.beforeInvocation(fi);源码
  17. //1.获取请求资源的权限
  18. //执行Collection<ConfigAttribute> attributes = SecurityMetadataSource.getAttributes(object);
  19. //2.是否拥有权限
  20. //this.accessDecisionManager.decide(authenticated, object, attributes);
  21. InterceptorStatusToken token = super.beforeInvocation(fi);
  22. try {
  23. fi.getChain().doFilter(fi.getRequest(), fi.getResponse());
  24. } finally {
  25. super.afterInvocation(token, null);
  26. }
  27. }
  28. public FilterInvocationSecurityMetadataSource getSecurityMetadataSource() {
  29. return securityMetadataSource;
  30. }
  31. public void setSecurityMetadataSource(FilterInvocationSecurityMetadataSource securityMetadataSource) {
  32. this.securityMetadataSource = securityMetadataSource;
  33. }
  34. public void init(FilterConfig arg0) throws ServletException {
  35. // TODO Auto-generated method stub
  36. }
  37. public void destroy() {
  38. // TODO Auto-generated method stub
  39. }
  40. @Override
  41. public Class<? extends Object> getSecureObjectClass() {
  42. //下面的MyAccessDecisionManager的supports方面必须放回true,否则会提醒类型错误
  43. return FilterInvocation.class;
  44. }
  45. }

核心的InterceptorStatusToken token = super.beforeInvocation(fi);会调用我们定义的accessDecisionManager:decide(Object object)和securityMetadataSource

:getAttributes(Object object)方法。

(2)MySecurityMetadataSource.java

  1. //1 加载资源与权限的对应关系
  2. public class MySecurityMetadataSource implements FilterInvocationSecurityMetadataSource {
  3. //由spring调用
  4. public MySecurityMetadataSource(ResourcesDao resourcesDao) {
  5. this.resourcesDao = resourcesDao;
  6. loadResourceDefine();
  7. }
  8. private ResourcesDao resourcesDao;
  9. private static Map<String, Collection<ConfigAttribute>> resourceMap = null;
  10. public ResourcesDao getResourcesDao() {
  11. return resourcesDao;
  12. }
  13. public void setResourcesDao(ResourcesDao resourcesDao) {
  14. this.resourcesDao = resourcesDao;
  15. }
  16. public Collection<ConfigAttribute> getAllConfigAttributes() {
  17. // TODO Auto-generated method stub
  18. return null;
  19. }
  20. public boolean supports(Class<?> clazz) {
  21. // TODO Auto-generated method stub
  22. return true;
  23. }
  24. //加载所有资源与权限的关系
  25. private void loadResourceDefine() {
  26. if(resourceMap == null) {
  27. resourceMap = new HashMap<String, Collection<ConfigAttribute>>();
  28. List<Resources> resources = this.resourcesDao.findAll();
  29. for (Resources resource : resources) {
  30. Collection<ConfigAttribute> configAttributes = new ArrayList<ConfigAttribute>();
  31. //以权限名封装为Spring的security Object
  32. ConfigAttribute configAttribute = new SecurityConfig(resource.getName());
  33. configAttributes.add(configAttribute);
  34. resourceMap.put(resource.getUrl(), configAttributes);
  35. }
  36. }
  37. Set<Entry<String, Collection<ConfigAttribute>>> resourceSet = resourceMap.entrySet();
  38. Iterator<Entry<String, Collection<ConfigAttribute>>> iterator = resourceSet.iterator();
  39. }
  40. //返回所请求资源所需要的权限
  41. public Collection<ConfigAttribute> getAttributes(Object object) throws IllegalArgumentException {
  42. String requestUrl = ((FilterInvocation) object).getRequestUrl();
  43. System.out.println("requestUrl is " + requestUrl);
  44. if(resourceMap == null) {
  45. loadResourceDefine();
  46. }
  47. return resourceMap.get(requestUrl);
  48. }
  49. }

这里的resourcesDao,熟悉Dao设计模式和Spring 注入的朋友应该看得明白。

(3)MyUserDetailServiceImpl.java

  1. public class MyUserDetailServiceImpl implements UserDetailsService {
  2. private UsersDao usersDao;
  3. public UsersDao getUsersDao() {
  4. return usersDao;
  5. }
  6. public void setUsersDao(UsersDao usersDao) {
  7. this.usersDao = usersDao;
  8. }
  9. public UserDetails loadUserByUsername(String username) throws UsernameNotFoundException {
  10. System.out.println("username is " + username);
  11. Users users = this.usersDao.findByName(username);
  12. if(users == null) {
  13. throw new UsernameNotFoundException(username);
  14. }
  15. Collection<GrantedAuthority> grantedAuths = obtionGrantedAuthorities(users);
  16. boolean enables = true;
  17. boolean accountNonExpired = true;
  18. boolean credentialsNonExpired = true;
  19. boolean accountNonLocked = true;
  20. User userdetail = new User(users.getAccount(), users.getPassword(), enables, accountNonExpired, credentialsNonExpired, accountNonLocked, grantedAuths);
  21. return userdetail;
  22. }
  23. //取得用户的权限
  24. private Set<GrantedAuthority> obtionGrantedAuthorities(Users user) {
  25. Set<GrantedAuthority> authSet = new HashSet<GrantedAuthority>();
  26. Set<Roles> roles = user.getRoles();
  27. for(Roles role : roles) {
  28. Set<Resources> tempRes = role.getResources();
  29. for(Resources res : tempRes) {
  30. authSet.add(new GrantedAuthorityImpl(res.getName()));
  31. s }
  32. }
  33. return authSet;
  34. }
  35. }

(4) MyAccessDecisionManager.java

  1. public class MyAccessDecisionManager implements AccessDecisionManager {
  2. public void decide(Authentication authentication, Object object, Collection<ConfigAttribute> configAttributes) throws AccessDeniedException, InsufficientAuthenticationException {
  3. if(configAttributes == null) {
  4. return;
  5. }
  6. //所请求的资源拥有的权限(一个资源对多个权限)
  7. Iterator<ConfigAttribute> iterator = configAttributes.iterator();
  8. while(iterator.hasNext()) {
  9. ConfigAttribute configAttribute = iterator.next();
  10. //访问所请求资源所需要的权限
  11. String needPermission = configAttribute.getAttribute();
  12. System.out.println("needPermission is " + needPermission);
  13. //用户所拥有的权限authentication
  14. for(GrantedAuthority ga : authentication.getAuthorities()) {
  15. if(needPermission.equals(ga.getAuthority())) {
  16. return;
  17. }
  18. }
  19. }
  20. //没有权限
  21. throw new AccessDeniedException(" 没有权限访问! ");
  22. }
  23. public boolean supports(ConfigAttribute attribute) {
  24. // TODO Auto-generated method stub
  25. return true;
  26. }
  27. public boolean supports(Class<?> clazz) {
  28. // TODO Auto-generated method stub
  29. return true;
  30. }
  31. }

三、流程

1)容器启动(MySecurityMetadataSource:loadResourceDefine加载系统资源与权限列表)
2)用户发出请求
3)过滤器拦截(MySecurityFilter:doFilter)
4)取得请求资源所需权限(MySecurityMetadataSource:getAttributes)
5)匹配用户拥有权限和请求权限(MyAccessDecisionManager:decide),如果用户没有相应的权限,

执行第6步,否则执行第7步。
6)登录
7)验证并授权(MyUserDetailServiceImpl:loadUserByUsername)
8)重复4,5

四、结束语

好了,终于写完了,回头看了一下,感觉不是怎么行。等我弄明白Spring Security它的原理之后,再回头修改下注释吧。大家觉得不妥的地方,可以留言,我会回复大家的。

    本站是提供个人知识管理的网络存储空间,所有内容均由用户发布,不代表本站观点。请注意甄别内容中的联系方式、诱导购买等信息,谨防诈骗。如发现有害或侵权内容,请点击一键举报。
    转藏 分享 献花(0

    0条评论

    发表

    请遵守用户 评论公约

    类似文章 更多