4:01 a.m.
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
Reporter: Ove Ranheim
Priority: Critical
Fix For: 3.1.0.CR1
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@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
4:05 a.m.
[
https://issues.jboss.org/browse/SEAMSECURITY-111?page=com.atlassian.jira....
]
Ove Ranheim updated SEAMSECURITY-111:
-------------------------------------
Environment:
JBoss AS 7.0.2.Final
Seam 3.1.0.Beta3
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
Priority: Critical
Fix For: 3.1.0.CR1
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@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
5:06 a.m.
[
https://issues.jboss.org/browse/SEAMSECURITY-111?page=com.atlassian.jira....
]
Shane Bryzak resolved SEAMSECURITY-111.
---------------------------------------
Assignee: Shane Bryzak
Resolution: Done
I got the example working with the latest snapshot of Seam Faces (it doesn't work with
Seam Faces 3.1.0.Beta3).
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.CR1
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@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
5:49 a.m.
[
https://issues.jboss.org/browse/SEAMSECURITY-111?page=com.atlassian.jira....
]
Ove Ranheim commented on SEAMSECURITY-111:
------------------------------------------
Built Faces from latest head and deployed. The error is still there. Please expand a
little when you say it doesn't work with Solder 3.1.0.Beta3. Authorization example
deploys just fine.
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.CR1
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@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
6:43 a.m.
[
https://issues.jboss.org/browse/SEAMSECURITY-111?page=com.atlassian.jira....
]
Ove Ranheim updated SEAMSECURITY-111:
-------------------------------------
Attachment: SecurityRulesTest.tgz
Please find the test case that demonstrates that ViewConfig is broken with regards to
SecurityRules.
See readme.txt for further details.
It might be that this issue is a Faces issue and not a Security issue.
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.CR1
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@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
7:36 a.m.
[
https://issues.jboss.org/browse/SEAMSECURITY-111?page=com.atlassian.jira....
]
Ove Ranheim edited comment on SEAMSECURITY-111 at 10/11/11 8:35 AM:
--------------------------------------------------------------------
Please find the attached test cases that demonstrates that ViewConfig is broken with
regards to SecurityRules.
See readme.txt for further details.
It might be that this issue is a Faces issue and not a Security issue.
was (Author: oranheim):
Please find the test case that demonstrates that ViewConfig is broken with regards to
SecurityRules.
See readme.txt for further details.
It might be that this issue is a Faces issue and not a Security issue.
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.CR1
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@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
2:44 a.m.
[
https://issues.jboss.org/browse/SEAMSECURITY-111?page=com.atlassian.jira....
]
Ove Ranheim commented on SEAMSECURITY-111:
------------------------------------------
To have correct behavior in SecurityRulesTest; Restrictions.checkGuest(Identity identity)
should be changed to:
{noformat}
public @Secures @Guest boolean checkGuest() {
return true;
}
{noformat}
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.CR1
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@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
5:15 p.m.
[
https://issues.jboss.org/browse/SEAMSECURITY-111?page=com.atlassian.jira....
]
Jason Porter updated SEAMSECURITY-111:
--------------------------------------
Fix Version/s: 3.1.0.Beta4
(was: 3.1.0.CR1)
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@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
2:38 a.m.
[
https://issues.jboss.org/browse/SEAMSECURITY-111?page=com.atlassian.jira....
]
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@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
4:33 a.m.
[
https://issues.jboss.org/browse/SEAMSECURITY-111?page=com.atlassian.jira....
]
Ove Ranheim commented on SEAMSECURITY-111:
------------------------------------------
I did a rewrite of the test today and to what I can see, it works just fine.
* Silly of me to have ViewConfig declared on class, not an interface. That was of course a
bug in the case
* Added a catch exception handler for AuthorizationException and now the circle is
complete
So, we can confluence @ViewConfig works as expect as of Solder/Seam Faces 3.1.0.Beta4.
However, the extension handling @ViewConfig should throw an exception when used on class
and not on interface.
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@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
5:11 p.m.
[
https://issues.jboss.org/browse/SEAMSECURITY-111?page=com.atlassian.jira....
]
Jason Porter commented on SEAMSECURITY-111:
-------------------------------------------
It currently logs a warning. An exception is probably better. Create a JIRA or pull
request?
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@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
4634
days inactive
4652
days old
10 comments
7 participants
participants (7)
-
Jason Porter (Commented) (JIRA) -
Jason Porter (Updated) (JIRA)
-
Ove Ranheim (Commented) (JIRA)
-
Ove Ranheim (Created) (JIRA)
-
Ove Ranheim (Issue Comment Edited) (JIRA)
-
Ove Ranheim (Updated) (JIRA)
-
Shane Bryzak (Resolved) (JIRA)