3.2. Configuring Data Grid Server endpoints
Control how the different server endpoints bind to sockets and use security realm configuration.
Prerequisites
- Add socket bindings and security realms to your Data Grid Server configuration.
Procedure
- Open your Data Grid Server configuration for editing.
-
Wrap multiple
endpointconfigurations with theendpointselement. -
Specify the socket binding that the endpoint uses with the
socket-bindingattribute. -
Specify the security realm that the endpoint uses with the
security-realmattribute. Disable administrator access with the
admin="false"attribute, if required.With this configuration users cannot access Data Grid Console or the Command Line Interface (CLI) from the endpoint.
- Save the changes to your configuration.
Data Grid Server must be configured with at least one endpoint which has a REST connector with administrative capabilities.
Multiple endpoint configuration
The following Data Grid Server configuration creates endpoints on separate socket bindings with dedicated security realms and disabling administrative access on the public endpoint:
XML
<server xmlns="urn:infinispan:server:16.0">
<endpoints>
<endpoint socket-binding="public"
security-realm="application-realm"
admin="false">
</endpoint>
<endpoint socket-binding="private"
security-realm="management-realm">
</endpoint>
</endpoints>
</server>
JSON
{
"server": {
"endpoints": [
{
"socket-binding": "public",
"security-realm": "application-realm",
"admin": "false"
},
{
"socket-binding": "private",
"security-realm": "management-realm"
}]
}
}
YAML
server:
endpoints:
- socketBinding: public
securityRealm: application-realm
admin: false
- socketBinding: private
securityRealm: management-realm