[jboss-jira] [JBoss JIRA] (WFLY-3932) Enable security manager via JBoss Modules

[David Lloyd (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Lloyd updated WFLY-3932:
------------------------------
    Description: 
In WildFly Core the security manager can be enabled via the {{-secmgr}} argument or setting the {{SECMGR=true}} environment variable. In order for this change to work correctly the {{WildFlySecurityManager.install()}} needs to be disabled.

Also -all- standalone, process-controller and host-controller modules that declare a dependency on {{org.wildfly.security.manager}} need to export the services.

The security manager test suite configuration needs to be updated to use the {{-secmgr}} argument rather than using {{-Dsecurity.manager}} to transform the profile (though the same system property should probably be reused to add the argument, like we had originally done).

Test suite configuration needs to be updated to *always* enable the security manager subsystem, even if the security manager is disabled.  This will cause the permissions to still be associated with deployments (though they will not be used unless -secmgr was passed to the startup script).

  was:
In WildFly Core the security manager can be enabled via the {{-secmgr}} argument or setting the {{SECMGR=true}} environment variable. In order for this change to work correctly the {{WildFlySecurityManager.install()}} needs to be disabled.

Also -all- standalone, process-controller and host-controller modules that declare a dependency on {{org.wildfly.security.manager}} need to export the services.

Tests need to be updated to use the {{-secmgr}} argument rather than {{-Djava.security.manager}}.



> Enable security manager via JBoss Modules
> -----------------------------------------
>
>                 Key: WFLY-3932
>                 URL: https://issues.jboss.org/browse/WFLY-3932
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Security Manager
>            Reporter: James Perkins
>            Assignee: James Perkins
>
> In WildFly Core the security manager can be enabled via the {{-secmgr}} argument or setting the {{SECMGR=true}} environment variable. In order for this change to work correctly the {{WildFlySecurityManager.install()}} needs to be disabled.
> Also -all- standalone, process-controller and host-controller modules that declare a dependency on {{org.wildfly.security.manager}} need to export the services.
> The security manager test suite configuration needs to be updated to use the {{-secmgr}} argument rather than using {{-Dsecurity.manager}} to transform the profile (though the same system property should probably be reused to add the argument, like we had originally done).
> Test suite configuration needs to be updated to *always* enable the security manager subsystem, even if the security manager is disabled.  This will cause the permissions to still be associated with deployments (though they will not be used unless -secmgr was passed to the startup script).



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)