geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Han Hong Fang (JIRA)" <j...@apache.org>
Subject [jira] Updated: (GERONIMO-5578) incorrect behaviour of security-constraint configuration in web.xml
Date Wed, 15 Sep 2010 02:35:32 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Han Hong Fang updated GERONIMO-5578:
------------------------------------

    Attachment: GERONIMO-5578.patch

A WebResourcePermission must be added to the corresponding role for each distinct combination
in the cross-product of url-pattern and role-name occurring in the security-constraint elements
that contain an auth-constraint naming roles.  (ref to chapter 3.1.3.2 of JACC v1.4 spec).


The problem existed becaused all role-name shared a WebResourcePermission for each url-pattern.

The patch is provided together with junit test case.

Please help to review. Thanks!

> incorrect behaviour of security-constraint configuration in web.xml 
> --------------------------------------------------------------------
>
>                 Key: GERONIMO-5578
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5578
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Tomcat
>    Affects Versions: 3.0
>            Reporter: Han Hong Fang
>            Assignee: Han Hong Fang
>         Attachments: GERONIMO-5578.patch
>
>
> When have following configuration in web.xml, GET and POST can be accessed by both "RoleA"
and "RoleB".
> <security-constraint>
>         <web-resource-collection>
>             <web-resource-name>resource2</web-resource-name>
>             <url-pattern>/SampleServlet2</url-pattern>
>             <http-method>GET</http-method>
>         </web-resource-collection>
>         <auth-constraint>
>             <role-name>RoleA</role-name>
>         </auth-constraint>
>     </security-constraint>
>     
>     <security-constraint>
>         <web-resource-collection>
>             <web-resource-name>resource3</web-resource-name>
>             <url-pattern>/SampleServlet2</url-pattern>
>             <http-method>POST</http-method>
>         </web-resource-collection>
>         <auth-constraint>
>             <role-name>RoleB</role-name>
>         </auth-constraint>
>     </security-constraint>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message