Remoting WildFly Subsystem Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 51: Line 51:
===<tt>security-realm</tt>===
===<tt>security-realm</tt>===


The presence of the '<tt>security-realm</tt>' attribute in the remoting connector configuration triggers enabling of authentication within the remoting service. For more details about remoting security see [[]].
The presence of the '<tt>security-realm</tt>' attribute in the remoting connector configuration triggers enabling of authentication within the remoting service. For more details about remoting security see [[Remoting_WildFly_Subsystem_Concepts#Security|Remoting Subsystem Concepts - Security]].


==<tt><http-connector></tt>==
==<tt><http-connector></tt>==


The <tt>connector-ref</tt> is the name of the [[Undertow WildFly Subsystem Configuration#http-listener|Undertow <tt>http-listener</tt>]], so if the name of that connector changes, the Remoting reference should also change.
The <tt>connector-ref</tt> is the name of the [[Undertow WildFly Subsystem Configuration#http-listener|Undertow <tt>http-listener</tt>]], so if the name of that connector changes, the Remoting reference should also change.

Revision as of 00:14, 12 April 2016

Internal

Overview

WildFly 9

<subsystem xmlns="urn:jboss:domain:remoting:3.0">
    <endpoint worker="default"/>
    <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>
</subsystem>

EAP 6.4

<subsystem xmlns="urn:jboss:domain:remoting:1.2">
    <connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/>
</subsystem>

<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
    ...
    <socket-binding name="remoting" port="4447"/>
    ...
</socket-binding-group>

Schema


https://github.com/wildfly/?

TODO: Link to .xsd.

Configuration Elements

<endpoint>

The Remoting endpoint uses the XNIO Worker declared and configured by the io subsystem. The XNIO worker's configuration is described here: io subsystem worker configuration.

<connector>

name

socket-binding

security-realm

The presence of the 'security-realm' attribute in the remoting connector configuration triggers enabling of authentication within the remoting service. For more details about remoting security see Remoting Subsystem Concepts - Security.

<http-connector>

The connector-ref is the name of the Undertow http-listener, so if the name of that connector changes, the Remoting reference should also change.