A client is authenticated when it connects, with valid credentials, to a GemFire cache server that is configured with the client
Once the client is authenticated, the server assigns the client a unique ID and principal, used to authorize operations. The client must trust all cache servers in the server system as it may connect to any one of them. For information on configuring client/server , see Client/Server Configuration.
Client connections can be authenticated at two levels, process and multiuser.
The native client uses system properties to acquire valid credentials for authentication by the server. You define these properties in the
geode.propertiesfile, which the native client accesses during startup.
When the cache server receives client credentials during the handshake operation, the server authenticates the client with the callback configured in the
security-client-authenticatorsystem property. The handshake succeeds or fails depending on the results of the authentication process.
To create multiple, secure connections to your servers from a single client, so the client can service different user types, you create an authenticated
RegionServicefor each user.
An LDAP server can be used by a GemFire cache server using the sample LDAP implementation provided with the GemFire server.