schemaorg_apache_xmlbeans.src.gateway-config-201409.xsd Maven / Gradle / Ivy
Configuration for the Kaazing gateway.
This is the top-level element of the gateway
configuration file.
This is the element for specifying
default values for parameters in the services.
This is the element for configuring a
service running on the gateway.
This is the element for configuring a
set of default accept-options, connect-options, mime-mapping for all services running
on the gateway.
This is the element for configuring
gateway security.
This is the element for gateway
cluster configuration.
This type describes the configuration of the
gateway's clustering behavior.
The protocol, network interface (possibly
internal), and the port number on which the
cluster accepts connections.
This type describes a mapping of a document filename extension
to a MIME content type string. The content type string would
typically be sent as a Content-Type header in an HTTP or other
response.
The file extension.
The MIME-type to send for the given extension.
This is the element for configuring the user roles
that are authorized to perform specific
operations.
The name of the user role to be included in the
authorization-constraint.
This is the element for configuring the
keystore that contains encryption keys for secure
communications with the gateway.
This is the element for configuring the
truststore that contains digital certificates for
certificate authorities trusted by the
gateway.
This is the element that associates an
authenticated user with a set of authorized
roles.
The name of the realm.
The description of the
realm.
The name of the class that represents a user
principal that an admin is interested in knowing about. When
a principal of this class is authenticated, a notification of
such will be sent via the management service. If no management
service is configured, then this element will be ignored.
The authentication for a realm defines how users
authenticate and become authorized for activity within the realm.
The scheme with which to challenge the client
when a service is accessed with missing or invalid credentials.
The authorization mode under which realm services operate.
The interval of time after which the web socket is closed.
One or more headers containing authentication data.
One or more query parameters containing authentication data.
One or more cookies containing authentication data.
The name of the security realm used for
authentication or * to indicate any valid
user.
The protocol scheme, fully qualified host
name, and port number of the cross-origin site that is
allowed to access this service. Specify the value * if you
want to allow access to all cross-site origin sites.
Specifying * may be for appropriate for services that
restrict HTTP methods or custom headers, but not the
origin of the request.
A comma-separated list of methods that can
be invoked by the cross-origin site.
A comma-separated list of custom header
names that can be sent by the cross-origin site when it
accesses the service.
This type of service is used to broadcast
information from a back-end service.
This type of service is used to load-balance WebSocket
requests.
This type of service is used to expose directories
or files hosted on the gateway.
This service provides echoing of input. Useful for
testing.
Represents extension services.
The name of the security realm used for
authentication or * to indicate any valid user.
This type of service is used to expose the AMQP proxy
service.
The name of the security realm used for
authentication or * to indicate any valid user.
This service provides reverse proxying of http requests.
This type of service is used to proxy connections
to a back-end service.
This type of service is used to check for gateway updates
The behavior of the login module at the time it
validates the user's credentials.
A comma-separated list of
SSL/TLS ciphersuite names to be used for this
connection.
A comma-separated list of
SSL/TLS protocol names to be used for this
connection. The protocols names are SSLv2Hello, SSLv3, TLSv1, TLSv1.1,
TLSv1.2. If not specified explicitly, SSLv3 protocol is not
enabled by default (as it is known to have vulnerabilities).
Specifies an interface to use for udp so that the multicast traffic can be constrained to a
specific interface.
A comma-separated list of
SSL/TLS ciphersuite names to be used for this
connection.
A comma-separated list of
SSL/TLS protocol names to be used for this
connection. The protocols names are SSLv2Hello, SSLv3, TLSv1, TLSv1.1,
TLSv1.2. If not specified explicitly, SSLv3 protocol is not
enabled by default (as it is known to have vulnerabilities).
HTTP keep-alive (or persistent connections) allow reuse of same TCP
connection for multiple HTTP request/responses. This will improve HTTP performance
esp for services like http proxy. This is enabled by default.
HTTP keep-alive (or persistent connections) allow reuse of same TCP
connection for multiple HTTP request/responses. If the TCP connection is idle
for the specified time, the connection is closed and will not be reused for
any further HTTP requests/responses.
Gateway caches the specified number of idle keep-alive (or persistent) connections
to upstream server in the cache of each worker. Those connections will timeout based on
keep-alive timeout config option. It is recommended to keep this number small enough to let
upstream servers process new incoming connections as well.
This config option does not limit the max number of connections to upstream server that
the gateway can open.
Specifies an interface to use for udp so that the multicast traffic can be constrained to a
specific interface.
AWS AccessKeyId of the account owner.
AWS SecretKey.
© 2015 - 2025 Weber Informatics LLC | Privacy Policy