[
https://issues.jboss.org/browse/WFLY-3932?page=com.atlassian.jira.plugin....
]
James Perkins 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.
Tests need to be updated to use the {{-secmgr}} argument rather than
{{-Djava.security.manager}}.
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 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.
Tests need to be updated to use the {{-secmgr}} argument rather than
{{-Djava.security.manager}}.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)