[[Configuring_other_clients_using_wildfly-config]]
= Client configuration using wildfly-config.xml
Prior to WildFly 11, many WildFly client libraries used different configuration strategies. WildFly 11 introduces a new `wildfly-config.xml` file which unifies all client configuration in a single place. In addition to being able to configure authentication using Elytron as described in the previous section, a `wildfly-config.xml` file can also be used to:
== Configure EJB client connections, global interceptors, and invocation timeout
Schema location: [https://github.com/wildfly/jboss-ejb-client/blob/4.0.2.Final/src/main/resources/schema/wildfly-client-ejb_3_0.xsd]
Example configuration:
.wildfly-config.xml
[source, xml]
----
...
...
----
== Configure HTTP client
Schema location:[https://github.com/wildfly/wildfly-http-client/blob/1.0.2.Final/common/src/main/resources/schema/wildfly-http-client_1_0.xsd]
Example configuration:
.wildfly-config.xml
[source, xml]
----
...
...
----
== Configure a remoting endpoint
Schema location:[https://github.com/jboss-remoting/jboss-remoting/blob/5.0.1.Final/src/main/resources/schema/jboss-remoting_5_0.xsd]
Example configuration:
.wildfly-config.xml
[source, xml]
----
...
...
----
== Configure the default XNIO worker
Schema location:[https://github.com/xnio/xnio/blob/3.5.1.Final/api/src/main/resources/schema/xnio_3_5.xsd]
Example configuration:
*wildfly-config.xml*
[source, xml]
----
...
...
----
[NOTE]
Note that WildFly client libraries do have reasonable default configuration. Thus, adding configuration for these clients to `wildfly-config.xml` isn’t mandatory.