Bug 1035378 - Procedure which setting Security Manager doesn't work on Windows in Security Guide
Summary: Procedure which setting Security Manager doesn't work on Windows in Security ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: EAP 6.2.2
Assignee: Tom WELLS
QA Contact: Ondrej Lukas
URL:
Whiteboard:
Depends On:
Blocks: 1035353
TreeView+ depends on / blocked
 
Reported: 2013-11-27 16:07 UTC by FIlip Bogyai
Modified: 2015-12-01 05:53 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Build Name: 14876, Security Guide-6.2-1 Build Date: 27-11-2013 14:15:01 Topic ID: 4779-458781 [Latest]
Last Closed: 2014-06-02 12:49:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description FIlip Bogyai 2013-11-27 16:07:55 UTC
In chapter 5.3. Run JBoss EAP 6 Within the Java Security Manager there is procedure for setting security manager, but it doesn't work on windows (there are standalone.conf.bat instead of standalone.conf, propetry are set through % instead of $ etc.). I think it should be explicitly mention it this procedure.

Comment 2 Josef Cacek 2014-04-22 18:57:38 UTC
Examples are not correct:

1) remove -Djava.security.debug=access:failure from all examples - it's a property which enables debugging and it's usually not used on production systems. We cover this property in another section of the chapter.

2)
Example 6.1. domain.conf - the JBOSS_HOME variable is not available in domain conf (cf. bug #1083474), so full path must be used.

3)
Example 6.2. domain.conf.bat - neither $PWD nor $JBOSS_HOME available (and wrong variable expansion used) - full paths should be used

4)
Example 6.4. standalone.conf.bat -  $PWD not available and wrong variable expansion for JBOSS_HOME - it should be %JBOSS_HOME%

Comment 4 Zbyněk Roubalík 2014-04-23 12:51:50 UTC
Verified on Revision 6.2.2-7


Note You need to log in before you can comment on or make changes to this bug.