Security: Authentication and Encryption
Most security configuration takes place on the Geode server. The server’s security framework authenticates clients as they connect to a cache server and authorizes client cache operations using developer-provided implementations for authentication and authorization.
For an explanation of the server-side implementation of security features, see Security in the Geode User Guide.
A Native Client application must address two security concerns when connecting to a Geode server:
The Client must submit its authentication credentials to the server using the developer-provided authentication implementation expected by the server.
TLS/SSL Client/Server Communication Encryption
Communication between client and server should be encrypted so authentication credentials and other transmissions cannot be viewed by third-parties.