[ https://issues.jboss.org/browse/REMJMX-78?page=com.atlassian.jira.plugin.... ] Carlo Bonamico commented on REMJMX-78: -------------------------------------- As a minimum, it would be necessary to allow for external configuration of the SSL options. If the server has a NON-SSL jmx connector, the client would not connect to it. The issue is with the class org.jboss.remoting3.jmx.RemotingConnector which initializes XNIO with a fixed, built-in OptionsMap, which cannot be overriden with properties from the environment map. Only the authentication credentials are passed on... // open a connection final IoFuture<Connection> futureConnection = endpoint.connect(convert(serviceUrl), getOptionMap(), handler); And this is currently the fixed map private OptionMap getOptionMap() { OptionMap.Builder builder = OptionMap.builder(); builder.set(SASL_POLICY_NOANONYMOUS, Boolean.FALSE); builder.set(SASL_POLICY_NOPLAINTEXT, Boolean.FALSE); List<Property> tempProperties = new ArrayList<Property>(1); tempProperties.add(Property.of("jboss.sasl.local-user.quiet-auth", "true")); builder.set(Options.SASL_PROPERTIES, Sequence.of(tempProperties)); builder.set(Options.SSL_ENABLED, true); builder.set(Options.SSL_STARTTLS, true); return builder.getMap(); } -- This message was sent by Atlassian JIRA (v6.2.6#6264)