Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 724559 (BRMS-508)

Summary: signed standalone fails to start due to security exception in brms.war
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: trev <tkirby>
Component: BRM (Guvnor)Assignee: trev <tkirby>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: urgent    
Version: 5.1.0.CR1CC: lcarlon, tsurdilo
Target Milestone: ---   
Target Release: BRMS 5.2.0.GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/BRMS-508
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
The signed standalone version of BRMS was failing to start due to a security exception in brms.war, the RoleBasePermissionResolver.class was moved to the org.drools.guvnor.client.security.permission package which resolved the issue.
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-25 16:05:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description trev 2010-12-08 16:34:53 UTC
securitylevel_name: Public

Security exception thrown on brms.war due to jboss-as-web/server/production/deploy/jboss-brms.war/WEB-INF/classes/org/jboss/seam/security/permission/RoleBasedPermissionResolver.class not being signed

 2010-12-08 15:27:52,664 INFO  [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/jboss-brms
2010-12-08 15:27:55,864 WARN  [org.jboss.detailed.classloader.ClassLoaderManager] (main) Unexpected error during load of:org.jboss.seam.security.permission.PermissionResolver
 java.lang.SecurityException: class "org.jboss.seam.security.permission.PermissionResolver"'s signer information does not match signer information of other classes in the same package

Comment 1 Tihomir Surdilovic 2010-12-08 19:12:43 UTC
moved RoleBasedPermissionResolver to the org.drools.guvnor.client.security.permission package which should fix this. 
please note that this fix requires a change in the documentation -> in components.xml from now on to configure role-based authentication it is no longer:

<security:role-based-permission-resolver
		enable-role-based-authorization="false" />

but

<component name="org.jboss.seam.security.roleBasedPermissionResolver">
    	<property name="enableRoleBasedAuthorization">false</property>
    </component>

where the value can be false (default) or true for users to set role based auth to true.

Comment 2 Tihomir Surdilovic 2010-12-08 19:18:37 UTC
Assigning to Neil to make sure he can sign the jars now

Comment 3 Tihomir Surdilovic 2010-12-08 21:02:55 UTC
Link: Added: This issue related GUVNOR-1120


Comment 4 lcarlon 2011-08-19 04:11:03 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Doc as known issue

Comment 5 lcarlon 2011-08-19 04:49:19 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-Doc as known issue+Need release note

Comment 6 lcarlon 2011-08-23 05:57:52 UTC
Doc bug raised to amend components.xml in the admin guide:

https://bugzilla.redhat.com/show_bug.cgi?id=732613

for future reference if documentation is required, please raise a docs bug.

Comment 7 lcarlon 2011-08-23 22:42:41 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1,3 @@
-Need release note+https://bugzilla.redhat.com/show_bug.cgi?id=724559
+
+The signed standalone version of BRMS was failing to start due to a security exception in brms.war, the RoleBasePermissionResolver.class was moved to the org.drools.guvnor.client.security.permission package which resolved the issue.

Comment 8 lcarlon 2011-09-14 04:31:15 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,3 +1 @@
-https://bugzilla.redhat.com/show_bug.cgi?id=724559
-
 The signed standalone version of BRMS was failing to start due to a security exception in brms.war, the RoleBasePermissionResolver.class was moved to the org.drools.guvnor.client.security.permission package which resolved the issue.