Bug 1035386

Summary: Wrong and unsatisfactory section Permission Specific to JBoss EAP 6 in Security Manager in Security Guide
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: FIlip Bogyai <fbogyai>
Component: DocumentationAssignee: Tom WELLS <twells>
Status: CLOSED DUPLICATE QA Contact: Ondrej Lukas <olukas>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: jkudrnac, lcarlon, twells
Target Milestone: ---Keywords: Documentation, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Build Name: 14876, Security Guide-6.2-1 Build Date: 27-11-2013 14:15:01 Topic ID: 4782-552816 [Latest]
Last Closed: 2014-04-19 17:12:55 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:
Bug Depends On:    
Bug Blocks: 1035353    

Description FIlip Bogyai 2013-11-27 16:14:33 UTC 
In 5.4. Write a Java Security Manager Policy is section Permission Specific to JBoss EAP 6 which is wrong and information there are unsatisfactory to write policy file configuration.
1) There are only names of permissions, but every permission needs to have defined type too. Without this knowledge of type this permission can't be used in policy file.
2) Names of permissions are outdated (probably from EAP5) and need to be renewed. These permissions come from different modules and for that reason every owner of module must specify, which permissions are needed for access to specific parts of his module.