]
Darran Lofthouse commented on WFLY-7047:
----------------------------------------
Once we reach phase IV of these pull requests I am hoping to completely eliminate these
*-elytron.xml configuration files and move Elytron over to the main default configuration
of a clean server so for now I don't think it will be beneficial to create forks of
the additional host-* files. Phase III may temporarily introduce them as that is where
full management integration will come in so they may be application and then depending on
what happens in Phase IV we can have a closer look at the default files then.
host-elytron.xml, different jvm settings, unnecesarry unsecure
interface
------------------------------------------------------------------------
Key: WFLY-7047
URL:
https://issues.jboss.org/browse/WFLY-7047
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 11.0.0.Alpha1
Reporter: Martin Choma
Assignee: Darran Lofthouse
Fix For: 11.0.0.Alpha1
host-elytron.xml, different jvm settings, unnecesarry unsecure interface
When I compare host-elytron.xml to host.xml,
1) jvm settings use permgen element
2) probably unnecesarry configuration of unsecure profile stays there
Is it worth provide elytron-like host-master/host-slave configuration files for
convenience?