[jboss-jira] [JBoss JIRA] (WFCORE-94) Add MODULE_OPTS 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=13008218#comment-13008218 ] 

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

Additional work needed:

* Include an update to all the main module.xml files to include a dependency on the security manager module (the external project, not the subsystem module) (with imported services)
* Include a patch to the security manager subsystem to disable the security manager install() that it does
* Wildfly security manager dependency version needs to be updated to one which includes the meta-inf machinery that JBoss Modules requires

> Add MODULE_OPTS 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)