[seam-issues] [JBoss JIRA] (SEAMSECURITY-111) Security rules is broken

Jason Porter (Commented) (JIRA) jira-events at lists.jboss.org
Thu Oct 27 03:38:45 EDT 2011


    [ https://issues.jboss.org/browse/SEAMSECURITY-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637922#comment-12637922 ] 

Jason Porter commented on SEAMSECURITY-111:
-------------------------------------------

It appears that things are working mostly correctly now. I had to tweak the test though.

* ViewConfig must be an interface otherwise none of the annotations on the enums are proccessed.
* I think you have an infinite loop as the AccessDenied page contains restrictions so it gets stuck.
* Removed the expected exception for test testAuthorizedPriveligedAction because it doesn't happen

Once I fixed those things then on the last test I get an error when it tries to redirect. I'm actually not sure if this is because Seam Servlet is causing a problem or something else. Please make the above changes and see if you can dig any further.
                
> Security rules is broken
> ------------------------
>
>                 Key: SEAMSECURITY-111
>                 URL: https://issues.jboss.org/browse/SEAMSECURITY-111
>             Project: Seam Security
>          Issue Type: Bug
>    Affects Versions: 3.1.0.Beta3
>         Environment: JBoss AS 7.0.2.Final
> Seam 3.1.0.Beta3
>            Reporter: Ove Ranheim
>            Assignee: Shane Bryzak
>            Priority: Critical
>             Fix For: 3.1.0.Beta4
>
>         Attachments: SecurityRulesTest.tgz
>
>
> Security rules is broken. If you deploy the Seam Security Authorization example and do a login. You will see the following error without any exception:
> 10:55:11,144 ERROR [org.jboss.weld.Bean] (http-192.168.0.199-192.168.0.199-8080-1) WELD-000019 Error destroying an instance Managed Bean [class org.jboss.seam.security.permission.SecurityRuleProducer] with qualifiers [@Any @Default] of org.jboss.seam.security.permission.SecurityRuleProducer at 350510c7
> The consequence is that no security rules (Restrictions) are being invoked after this error occurs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the seam-issues mailing list