-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
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.
- blocks
-
WFCORE-258 Enable security manager via JBoss Modules
- Resolved
-
WFLY-4091 Disable WildFlySecurtyManager.install() in security manager subsystem
- Closed
- is blocked by
-
WFCORE-147 Update wildfly-security-manager from 1.0.1.Final to 1.1.0.Final
- Resolved