[ https://issues.redhat.com/browse/WFLY-717?page=com.atlassian.jira.plugin.... ] Brian Stansberry resolved WFLY-717. ----------------------------------- Fix Version/s: (was: Awaiting Volunteers) Assignee: (was: Pete Muir) Resolution: Won't Do Thanks, [~oranheim] for the instructions on how to do this for those who want it. I'm resolving this as 'Won't Do' as I don't see this as a proper feature of WildFly itself. Exposing the H2 console is nice for dev use cases but if not done carefully it creates security risks, as the console lets you do a lot more than just examine the data produced by your WildFly app. The basic answer to those risks is "don't expose the console to an untrusted network." If WildFly itself adds a feature that exposes the console we are then somewhat responsible for whether or not it is exposed safely. I don't think that's a responsibility the WildFly project should take on. -- This message was sent by Atlassian Jira (v7.13.8#713008)