Managing Kerberos and Other Authentication Services in Oracle® Solaris 11.2

Exit Print View

Updated: August 2014

Number of Slave KDCs

Slave KDCs generate credentials for clients just as the master KDC does. Slave KDCs provide backup if the master becomes unavailable. Plan to create at least one slave KDC per realm.

    Additional slave KDCs might be required depending on the following factors:

  • The number of physical segments in the realm. Normally, the network should be set up so that each segment can function, at least minimally, without the rest of the realm. To do so, a KDC must be accessible from each segment. The KDC in this instance could be either a master or a slave.

  • The number of clients in the realm. By adding more slave KDC servers, you can reduce the load on the current servers.

Avoid adding too many slave KDCs. Because the KDC database must be propagated to each server, the more KDC servers that are installed, the longer it can take to get the data updated throughout the realm. Also, because each slave retains a copy of the KDC database, more slaves increase the risk of a security breach.

Configure one or more slave KDCs to be swapped with the master KDC. The advantage of configuring at least one slave KDC in this way is that if the master KDC fails for any reason, you will have a system preconfigured to become the master KDC. For instructions, see Swapping a Master KDC and a Slave KDC.