[
https://issues.jboss.org/browse/WFLY-10242?page=com.atlassian.jira.plugin...
]
David Lloyd edited comment on WFLY-10242 at 5/11/18 4:02 PM:
-------------------------------------------------------------
If they're using any WildFly version since 10, and they want a security manager to be
present during their particular execution, then they have the option of passing the
{{-secmgr}} switch to any* script as an argument, or they may alternatively set the
{{SECMGR}} environment variable to {{true}} (if it is inconvenient to modify the script
argument list for whatever reason).
\* Of course we don't have uniform support for this, but that's what this JIRA is
about, in essence.
was (Author: dmlloyd):
If they're using any WildFly version since 10, and they want a security manager to be
present during their particular execution, then they have the option of passing the
{{-secmgr}} switch to any* script as an argument, or they may alternatively set the
{{SECMGR}} environment variable to {{true}} (if it is inconvenient to modify the script
argument list for whatever reason).
* Of course we don't have uniform support for this, but that's what this JIRA is
about, in essence.
Unify secmgr JAVA_OPTS behaviour in WF scripts
----------------------------------------------
Key: WFLY-10242
URL:
https://issues.jboss.org/browse/WFLY-10242
Project: WildFly
Issue Type: Bug
Components: Scripts
Reporter: Marek Kopecký
Assignee: Kabir Khan
Unify secmgr JAVA_OPTS behaviour in WF scripts.
standalone&&domain&&appclient scripts doesn't allow to use secmgr by
JAVA_OPTS definition. wsconsume&&wsprovide scripts allow that (see
[
this|https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main...]
and
[
this|https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main...])
All scripts should be unified.
cc: [~asoldano], [~jamezp], [~jbliznak], [~msvehla]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)