[
https://issues.jboss.org/browse/WFLY-10286?page=com.atlassian.jira.plugin...
]
Jean-Francois Denise commented on WFLY-10286:
---------------------------------------------
In both cases (CLI, JDR), if we don't have a strong requirement for it, I would not
invest in making changes to scripts. User can make changes directly in existing scripts if
he has such an (un-common?) need.
Enabling the security-manager can have large side effect on the CLI. But here we are
speaking about the JBOSS Module Security-Manager setup. All builtin modules are granted
all permissions, so we are safe.
I would say that it makes sense to have this option to allow to start an embedded server
with JBOSS module security manager enabled. Doing so you can reproduce a standalone
context.
I would be on the same line as
https://issues.jboss.org/browse/WFLY-10242?focusedCommentId=13561804&...
An explicit -secmgr option (with the proper help to explain the embedded use-case) and
SECMGR env.
For JDR, if it makes sense to have it enabled then same approach should be chosen.
[~bmaxwell]?
Consider to add secmgr options to CLI and JDR
---------------------------------------------
Key: WFLY-10286
URL:
https://issues.jboss.org/browse/WFLY-10286
Project: WildFly
Issue Type: Bug
Components: CLI, Scripts
Reporter: Marek Kopecký
Assignee: Jean-Francois Denise
Wildfly standalone/domain/appclient scripts allows two ways for start EAP with security
manager:
* -secmgr command line argument ({{./standalone.sh -secmgr}})
** This is described in documentation only in Configuration guide in "A.1. Server
Runtime Arguments"
* SECMGR=true env property
** This is not described in documentation at all.
Does it make sence to add secmgr parameter to CLI script? CLI allows to start embedded
server, and standalone.sh (non-embedded server) script has the secmgr option. Does it make
sence to add secmgr parameter to the jdr script too? JDR tool uses embedded cli server too
in some cases.
Cc: [~eduda], [~mnovak])
See [this my
command|https://issues.jboss.org/browse/WFLY-10242?focusedCommentId=13561...]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)