[ https://issues.jboss.org/browse/WFLY-1548?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1548: ----------------------------------------------- Darran Lofthouse <darran.lofthouse(a)redhat.com&gt; made a comment on [bug 901311|https://bugzilla.redhat.com/show_bug.cgi?id=901311] Not sure why this has a dev ack as I have already removed it once. I do not agree that there should be any attempt to automatically connect to the server if the user has chosen a local connection, the moment we move away from local authentication any attempts to automatically connect fail as there is no mechanism to obtain the users username and password. Where jconsole is connected to the process locally I suggest two alternatives: - - Add the CLI tab but with a clear message stating why the CLI is not currently available, potentially add an 'Establish Connection' button to the tab with the capability to prompt for a username and password if required and make use of the discovered address. - Add an MBean that can handle management ops, the CLI integration can use that MBean regardless of the connection method and would not require the establishment of additional connections. Due to the domain management implications there would be a few parties interested in this so I suggest we get a new discussion started on the dev list. However as I have said elsehwere I think this is attempting to fix a 'feature' that should not exist in it's current form anyway and the current approach whilst it fixes the current problem leaves it open for the next issue to be raised against it once something like the authentication requirements are changed. What we do need is the overall solution that works with the out of the box configuration but is flexible enough to cope with changes to this configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira