[jboss-jira] [JBoss JIRA] (WFCORE-94) Add -secmgr to startup scripts and propagate -secmgr through the domain

[David Lloyd (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008830#comment-13008830 ] 

David Lloyd commented on WFCORE-94:
-----------------------------------

Yes it can; after this change, enabling security manager no longer means adding the system (instead the subsystem will always be added).  To test with security manager, the -secmgr flag would be given at boot, meaning both core and full can be tested with and without security manager enabled.

> Add -secmgr to startup scripts and propagate -secmgr through the domain
> -----------------------------------------------------------------------
>
>                 Key: WFCORE-94
>                 URL: https://issues.jboss.org/browse/WFCORE-94
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: Domain Management, Scripts
>            Reporter: Kabir Khan
>            Assignee: James Perkins
>             Fix For: 1.0.0.Alpha9
>
>
> The preferred mechanism to enable a security manager is to use the -secmgr module option. Modify the scripts to make this easier to add, and make adjustments to propagate this through the domain.
> The -secmgr module option is not visible from the launched process, so for the process controller and host controller to pass that on to the started host controller or server process respectively, a check is added to see if a security manager was enabeld. If a security manager is enabled, and -Djava.security.manager is not present in the system properties, we add the -secmgr module option when starting the next process.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)