@@ -78,7 +78,10 @@ image::screenshots/add-firewall-rule.png[Adding firewall rule in a PowerShell wi
7878
7979=== Kerberos configuration file
8080
81- Java searches its Kerberos configuration in the `krb5.ini` file.
81+ Java searches the Kerberos realms configuration in the `krb5.ini` file on Windows.
82+ The file contains the address of the Key Distribution Center (KDC) - i.e. Active
83+ Directory server in our case.
84+
8285So let's create one simple configuration file `C:\Windows\krb5.ini`
8386on both servers.
8487
@@ -174,6 +177,18 @@ a new Hazelcast cluster with both members.
174177.Screenshot - Running Hazelcast cluster
175178image::screenshots/client-running.png[Running Hazelcast cluster.]
176179
180+ Within the `security` configuration, we defined which realm is used for
181+ the member-to-member authentication (`kerberosRealm`).
182+
183+ The security realm itself has two configuration parts:
184+
185+ - `authentication` - responsible for verifying incoming connections and mapping client roles;
186+ - `identity` - defines a member's credentials - used to prove its own identity to other members.
187+
188+ The most important options in the `kerberos` authentication and `kerberos` identity configurations
189+ are the `principal` (defines own Kerberos name) and `keytab-file` (file containing secrets of
190+ given principal).
191+
177192=== Simple Kerberos configuration warnings
178193
179194A warning message is printed to the console when the simple Kerberos configuration form is
@@ -399,4 +414,4 @@ The client authorization was based on group membership defined in the Active Dir
399414== See Also
400415
401416- https://docs.hazelcast.org/docs/4.1/manual/html-single/index.html#kerberos-authentication[Kerberos authentication] section in Hazelcast Reference manual
402- -
417+ - https://docs.oracle.com/en/java/javase/11/docs/api/jdk.security.auth/com/sun/security/auth/module/Krb5LoginModule.html[Krb5LoginModule] documentation
0 commit comments