3

对于通过 http 命名空间定义为拦截 URL 但在使用 JSP Authorize taglib 的表达式中定义的 Web 安全表达式，会考虑 roleHeirarchies。

我已经读了很多东西... ref1 ref2 ref3 ref4 ref5 ref6

****编辑：**** Ref1 和 Ref6 提到了有关过滤器顺序问题和 jsp 中不可用的安全上下文的问题......（顺便说一句，我正在使用 jsf2）也许有一些东西要挖掘...... .

编辑 2： JSF 是否处理安全标签库？我读了这个并尝试了没有成功

编辑 3 : : 我尝试通过 Maven spring-faces 2.3.2 和 spring-security-taglibs 安装...什么也没有发生...一些 tuto 说要创建一个自定义 taglib.xml 但它也没有用，我想它是为旧版本...

我测试了这个 facesContext.externalContext.isUserInRole('ROLE') 和 sec:authorize access="hasRole('Role')... 只有当它是相同的 ROLE 但它没有考虑到层次结构的东西... sec: autorize 什么都不做，所有的角色都被打印出来。

请参阅上面带有 ROLE ROLE_ADMIN_PROFILER_NGS 的用户的示例：

    <h:outputText rendered="#{facesContext.externalContext.isUserInRole('ROLE_ADMIN_PROFILER_NGS')}"  value ="ROLE_ADMIN_PROFILER_NGS"></h:outputText> // WORKS <br></br>
<h:outputText rendered="#{facesContext.externalContext.isUserInRole('ROLE_GUEST')}"  value ="ROLE_GUEST"></h:outputText> // SHOULD APPEAR BUT NOTHING HAPPENS<br></br>
<h:outputText rendered="#{facesContext.externalContext.isUserInRole('ROLE_ADMIN')}"  value ="ROLE_ADMIN"> // SHOULD NOT APPEAR AND THAT'S THE CASE</h:outputText><br></br>

/* ALL THE THREE NEXT ARE DISPLAYED WHITHOUT CONTROL AUTORIZATION.*/

<sec:authorize access="hasRole('ROLE_ADMIN_PROFILER_NGS')">ROLE_ADMIN_PROFILER_NGS<br></br></sec:authorize>
<sec:authorize access="hasRole('ROLE_GUEST')">ROLE_GUEST <br></br></sec:authorize>
<sec:authorize access="hasRole('ROLE_ADMIN')">ROLE_ADMIN  <br></br></sec:authorize>

这是我尝试访问以使用角色层次结构进行测试的内容：

当用户仅带有角色 GUEST 时...显示所有标签...它们不会出现，只有 GUEST（参见底部的定义）应该出现：

    <sec:authentication property="username" />
    <sec:authorize access="hasRole('ROLE_BABAB')">BABA</sec:authorize>
    <sec:authorize access="hasRole('ROLE_GUEST')">GUEST</sec:authorize>
    <sec:authorize access="hasRole('ROLE_ADMIN')">ADMIN</sec:authorize>

这是我的安全配置： 

   <security:http auto-config="true" access-decision-manager-ref="accessDecisionManager" use-expressions="true" disable-url-rewriting="true">
    <security:intercept-url pattern="/Participant/New/*" access="hasRole('ROLE_ADMIN')" />  
    <security:intercept-url pattern="/Home" access="hasRole('ROLE_GUEST')" />  
    <security:intercept-url pattern="/Login" access="hasRole('ROLE_ANONYMOUS')" />   
     <security:intercept-url pattern="/Login/Error" access="hasRole('ROLE_ANONYMOUS')" />    
    <security:form-login  login-page="/Login"  login-processing-url="/j_spring_security_check"  authentication-failure-url="/Login/Error" default-target-url="/Home" />
    <security:logout logout-url="/j_spring_security_logout" logout-success-url="/Home" delete-cookies="JSESSIONID"  invalidate-session="true"/>
    <security:anonymous/>
     <security:expression-handler ref="defaultWebSecurityExpressionHandler" />
    <security:session-management invalid-session-url="/Login" >
        <security:concurrency-control max-sessions="1" error-if-maximum-exceeded="true"  />
    </security:session-management>
   <security:port-mappings>
     <security:port-mapping http="8086" https="8443"/>
    </security:port-mappings>
  </security:http>

<beans:bean id="defaultWebSecurityExpressionHandler" class="org.springframework.security.web.access.expression.DefaultWebSecurityExpressionHandler">
      <beans:property name="roleHierarchy" ref="roleHierarchy"/>
</beans:bean>

<beans:bean id="accessDecisionManager" class="org.springframework.security.access.vote.AffirmativeBased">
  <beans:property name="decisionVoters">
    <beans:list>
       <beans:ref bean="roleVoter" />
        <beans:bean class="org.springframework.security.web.access.expression.WebExpressionVoter">
            <beans:property name="expressionHandler" ref="defaultWebSecurityExpressionHandler"/>
        </beans:bean>
       <beans:bean class="org.springframework.security.access.vote.AuthenticatedVoter"/>

    </beans:list>
  </beans:property>
</beans:bean>


<beans:bean id="roleVoter" class="org.springframework.security.access.vote.RoleHierarchyVoter">
    <beans:constructor-arg ref="roleHierarchy" />
</beans:bean>

<beans:bean id="roleHierarchy" class="org.springframework.security.access.hierarchicalroles.RoleHierarchyImpl">
    <beans:property name="hierarchy">
        <beans:value>
            ROLE_ADMIN > ROLE_ADMIN_PROFILER_NGS
            ROLE_ADMIN_PROFILER_NGS > ROLE_GUEST
            ROLE_GUEST > ROLE_GUEST_PROFILER_NGS  
            ROLE_ADMIN > ROLE_ADMIN_PROFILER_CGH
            ROLE_ADMIN_PROFILER_CGH > ROLE_GUEST
            ROLE_GUEST > ROLE_GUEST_PROFILER_CGH
        </beans:value>
    </beans:property>
 </beans:bean>

非常感谢，如果您有其他想法要测试，欢迎您...

编辑 3：

为什么它为 RoleHierarchyVoter 返回 0，而为 WebExpressionVoter 返回 1...正常吗？

14:48:32,861 调试 FilterSecurityInterceptor:194 - 安全对象：FilterInvocation：URL：/Home；属性：[hasRole('ROLE_GUEST')] 14:48:32,861 DEBUG FilterSecurityInterceptor:310 - 先前已验证：org.springframework.security.authentication.UsernamePasswordAuthenticationToken@43a64f5f：主体：com.clb.genomic.lyon.model.User@d46 : 用户名: jp; 密码保护]; 启用：真；AccountNonExpired：真；凭据非过期：真；AccountNonLocked：真；授予权限：ROLE_ADMIN_PROFILER_NGS；凭证：[受保护]；已认证：真实；详细信息：org.springframework.security.web.authentication.WebAuthenticationDetails@0：RemoteIpAddress：192.168.154.18；会话ID：084939D4E097F41ACA6A1F24CD8390BE；授予权限：ROLE_ADMIN_PROFILER_NGS 14:48:32,861 DEBUG RoleHierarchyImpl：117 - getReachableGrantedAuthorities() - 从角色 [ROLE_ADMIN_PROFILER_NGS] 可以通过零个或多个步骤到达 [ROLE_GUEST_PROFILER_NGS, ROLE_GUEST_PROFILER_CGH, ROLE_ADMIN_PROFILER_NGS, ROLE_GUEST]。14:48:32,861 DEBUG AffirmativeBased:65 - 投票者：org.springframework.security.access.vote.RoleHierarchyVoter@6ff43d69，返回：0 14:48:32,862 DEBUG RoleHierarchyImpl:117 - getReachableGrantedAuthorities() - 来自角色 [ROLE_ADMIN_PROFILER_NGS] 之一可以通过零个或多个步骤到达 [ROLE_GUEST_PROFILER_NGS, ROLE_GUEST_PROFILER_CGH, ROLE_ADMIN_PROFILER_NGS, ROLE_GUEST]。14:48:32,862 DEBUG AffirmativeBased:65 - 投票者：org.springframework.security.web.access.expression.WebExpressionVoter@3fe932d5，返回：1 14:48:32,862 DEBUG FilterSecurityInterceptor:215 - 授权成功 ROLE_ADMIN_PROFILER_NGS, ROLE_GUEST] 零个或多个步骤。14:48:32,861 DEBUG AffirmativeBased:65 - 投票者：org.springframework.security.access.vote.RoleHierarchyVoter@6ff43d69，返回：0 14:48:32,862 DEBUG RoleHierarchyImpl:117 - getReachableGrantedAuthorities() - 来自角色 [ROLE_ADMIN_PROFILER_NGS] 之一可以通过零个或多个步骤到达 [ROLE_GUEST_PROFILER_NGS, ROLE_GUEST_PROFILER_CGH, ROLE_ADMIN_PROFILER_NGS, ROLE_GUEST]。14:48:32,862 DEBUG AffirmativeBased:65 - 投票者：org.springframework.security.web.access.expression.WebExpressionVoter@3fe932d5，返回：1 14:48:32,862 DEBUG FilterSecurityInterceptor:215 - 授权成功 ROLE_ADMIN_PROFILER_NGS, ROLE_GUEST] 零个或多个步骤。14:48:32,861 DEBUG AffirmativeBased:65 - 投票者：org.springframework.security.access.vote.RoleHierarchyVoter@6ff43d69，返回：0 14:48:32,862 DEBUG RoleHierarchyImpl:117 - getReachableGrantedAuthorities() - 来自角色 [ROLE_ADMIN_PROFILER_NGS] 之一可以通过零个或多个步骤到达 [ROLE_GUEST_PROFILER_NGS, ROLE_GUEST_PROFILER_CGH, ROLE_ADMIN_PROFILER_NGS, ROLE_GUEST]。14:48:32,862 DEBUG AffirmativeBased:65 - 投票者：org.springframework.security.web.access.expression.WebExpressionVoter@3fe932d5，返回：1 14:48:32,862 DEBUG FilterSecurityInterceptor:215 - 授权成功 862 DEBUG RoleHierarchyImpl:117 - getReachableGrantedAuthorities() - 从角色 [ROLE_ADMIN_PROFILER_NGS] 可以通过零个或多个步骤到达 [ROLE_GUEST_PROFILER_NGS, ROLE_GUEST_PROFILER_CGH, ROLE_ADMIN_PROFILER_NGS, ROLE_GUEST]。14:48:32,862 DEBUG AffirmativeBased:65 - 投票者：org.springframework.security.web.access.expression.WebExpressionVoter@3fe932d5，返回：1 14:48:32,862 DEBUG FilterSecurityInterceptor:215 - 授权成功 862 DEBUG RoleHierarchyImpl:117 - getReachableGrantedAuthorities() - 从角色 [ROLE_ADMIN_PROFILER_NGS] 可以通过零个或多个步骤到达 [ROLE_GUEST_PROFILER_NGS, ROLE_GUEST_PROFILER_CGH, ROLE_ADMIN_PROFILER_NGS, ROLE_GUEST]。14:48:32,862 DEBUG AffirmativeBased:65 - 投票者：org.springframework.security.web.access.expression.WebExpressionVoter@3fe932d5，返回：1 14:48:32,862 DEBUG FilterSecurityInterceptor:215 - 授权成功

编辑 5： 

     <beans:bean id="login" class="com.clb.genomic.lyon.beans.LoginBean" scope ="session">
          <beans:property name="authenticationManager" ref="authenticationManager" /> 
     </beans:bean>

>     <security:authentication-manager alias="authenticationManager">
>         <security:authentication-provider user-service-ref="userBo" >
>             <security:password-encoder ref="standardPasswordEncoder"/>   
>         </security:authentication-provider>
>     </security:authentication-manager>
4

1 回答 1

1

在所有正确的地方设置 RoleHiarchy 可能非常具有挑战性。Spring WebFlow 目前重新实现了许多特性（即，它重新实现了标记库而不是从 Spring Security 的基本标记扩展），因此这种方法不太可能奏效。

与 JSF 无缝协作的另一种方法是创建一个RoleHierarchyAuthoritiesMapper并将其插入到您的 AuthenticationProvider 中。例如，以下配置应该为您提供您正在寻找的层次结构。

<security:http auto-config="true"
               use-expressions="true"
               disable-url-rewriting="true">
    <security:intercept-url pattern="/Participant/New/*"
        access="hasRole('ROLE_ADMIN')" />
    <security:intercept-url pattern="/Home"
        access="hasRole('ROLE_GUEST')" />
    <security:intercept-url pattern="/Login"
        access="hasRole('ROLE_ANONYMOUS')" />
    <security:intercept-url pattern="/Login/Error"
        access="hasRole('ROLE_ANONYMOUS')" />
    <security:form-login login-page="/Login"
        login-processing-url="/j_spring_security_check"
        authentication-failure-url="/Login/Error" default-target-url="/Home" />
    <security:logout logout-url="/j_spring_security_logout"
        logout-success-url="/Home" delete-cookies="JSESSIONID"
        invalidate-session="true" />
    <security:anonymous />

    <security:session-management invalid-session-url="/Login">
        <security:concurrency-control max-sessions="1"
                                      error-if-maximum-exceeded="true" />
    </security:session-management>
    <security:port-mappings>
        <security:port-mapping http="8086" https="8443" />
    </security:port-mappings>
</security:http>


<beans:bean id="authenticationProvider" class="org.springframework.security.authentication.dao.DaoAuthenticationProvider">
    <beans:property name="userDetailsService" ref="userDetailsService"/>
    <beans:property name="authoritiesMapper">
        <beans:bean class="org.springframework.security.access.hierarchicalroles.RoleHierarchyAuthoritiesMapper">
            <beans:constructor-arg ref="roleHierarchy"/>
        </beans:bean>
    </beans:property>
    <beans:property name="passwordEncoder">
        <beans:bean class="org.springframework.security.authentication.encoding.Md5PasswordEncoder"/>
    </beans:property>
</beans:bean>
<beans:bean id="roleHierarchy" class="org.springframework.security.access.hierarchicalroles.RoleHierarchyImpl">
    <beans:property name="hierarchy">
        <beans:value>
            ROLE_ADMIN > ROLE_ADMIN_PROFILER_NGS
            ROLE_ADMIN_PROFILER_NGS > ROLE_GUEST
            ROLE_GUEST > ROLE_GUEST_PROFILER_NGS
            ROLE_ADMIN > ROLE_ADMIN_PROFILER_CGH
            ROLE_ADMIN_PROFILER_CGH > ROLE_GUEST
            ROLE_GUEST > ROLE_GUEST_PROFILER_CGH
        </beans:value>
    </beans:property>
 </beans:bean>

<security:user-service id="userDetailsService">
    <security:user name="joe" password="bf403351dfb2ae819874163aff25a49c"
        authorities="ROLE_ADMIN" />
    <security:user name="pete" password="5d2ea1f70185e4357183bb9c00187219"
        authorities="ROLE_ADMIN_PROFILER_CGH" />
</security:user-service>

一些额外的亮点是我们不再需要以下 bean：

  • 访问决策管理器
  • 默认WebSecurityExpressionHandler
  • 角色投票者
于 2013-11-01T21:56:54.277 回答