Bug 1035838

Summary: Document difference between "=" and "==" in setting of java.security.policy in Security Guide
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Ondrej Lukas <olukas>
Component: DocumentationAssignee: Tom WELLS <twells>
Status: CLOSED CURRENTRELEASE QA Contact: Russell Dickenson <rdickens>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: jcacek, lcarlon, lcosti, twells
Target Milestone: GAKeywords: Documentation, Triaged
Target Release: EAP 6.2.2   
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: 28-11-2013 11:27:34 Topic ID: 4781-435838 [Latest]
Last Closed: 2014-06-02 12:50:13 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 Ondrej Lukas 2013-11-28 15:28:40 UTC 
Chapter 5. Java Security Manager (probably in section 5.2. About Java Security Manager Policies or 5.3. Run JBoss EAP 6 Within the Java Security Manager) should contain any mention about difference between using "=" and "==" in setting of java.security.policy property. Using java.security.policy==some.policy means that security manager uses only policy file which is set in java.security.policy property. Using java.security.policy=some.policy means that security manager uses policy from java.security.policy combined with policy set in policy.url part of java.home/lib/security/java.security. You can see at http://docs.oracle.com/javase/7/docs/technotes/guides/security/PolicyFiles.html#DefaultLocs to part "Specifying an Additional Policy File at Runtime" for this information. It can be a little confuse and I think it should be documented on some of places mentioned above.
Comment 3 Josef Cacek 2014-04-23 08:44:43 UTC 
Verified on docs-stage:
Revision 6.2.2-6
Revision 6.3.0-12