Hazelcast Security

Hazelcast is embedded in the openLooKeng. When hazelcast is used in openLooKeng, in order to ensure the communication security between the client and the server of hazelcast, as well as between the members of each server, It is recommended to enable hazelcast authentication and SSL/TLS channel encryption.

Hazelcast Authentication

Hazelcast only supports Kerberos authentication. Because the hazelcast is used by state-store module, so user wants to enable Hazelcast authentication, the state-store has to enable first.

When state-store enabled, add the following configuration in the state-store.properties:

hazelcast.kerberos.enableEnable Hazelcast authentication, the default value is false.
hazelcast.kerberos.login.context.nameThe context name to login the kerberos.
hazelcast.kerberos.service.principalThe service principal name of kerberos
hazelcast.kerberos.krb5.confThe location of the Kerberos configuration file.
hazelcast.kerberos.auth.login.configThe location of the configuration file to login the kerberos

The format of the configuration file jass.conf to login the kerberos is as the following. User has to create a principal in the kerberos first and configure the principal and the keytab.

Hazelcast {
com.sun.security.auth.module.Krb5LoginModule required
principalThe principal name to login the Kerberos
keyTabThe location of the keytab that can be used to authenticate the Kerberos principal.


All of the nodes must use the same configuration, including the kerberos principal and keytab.

Hazelcast SSL/TLS

SSL/TLS is configured in the state-store.properties. The same configuration is used on all nodes that need to use state store. After SSL/TLS is enabled, nodes that have not been configured SSL/ TLS is or configured incorrectly, will not be able to communicate with other nodes.

To enable SSL/TLS for Hazelcast, do the following:

  1. Generate Java keystore file. You can use the fully-qualified host name of each host to create a unique certificate for each node, which contains the key store of all public keys of all hosts, and provides a specifies the keystore. In most cases, it is more convenient to use wildcards to create certificates, as follows:

    keytool -genkeypair -alias openLooKeng -keyalg EC -keysize 256 -validity 365 -keystore keystore.jks -storepass <password>
        What is your first and last name?
          [Unknown]:  *.example.com
        What is the name of your organizational unit?
        What is the name of your organization?
        What is the name of your City or Locality?
        What is the name of your State or Province?
        What is the two-letter country code for this unit?
        Is CN=*.example.com, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?
          [no]:  yes
        Enter key password for <openLooKeng>
        	(RETURN if same as keystore password):
  2. Distribute the Java keystore file to other nodes.

  3. Enable the SSL/TLS of Hazelcast in state-store.properties.

    hazelcast.ssl.keystore.path=<keystore path>
    hazelcast.ssl.keystore.password=<keystore pasword>
    hazelcast.ssl.cipher.suites=<cipher suite list>
    hazelcast.ssl.protocols=<ssl protocol list>

    Suggested cipher suite is TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256.

    Suggested ssl protocol is TLS1.2 or TLS1.3.