Planning Your Installation
Your Kerberos implementation will be an important part of your network. As such, the Kerberos service needs to be always available, responsive, and in the event of failure, easily restored from backup. Therefore, integrating Kerberos authentication into your network calls for some planning.
The first consideration is what exactly you’ll be using Kerberos for. The answer to this question depends on whether you’ll need compatibility with Kerberos 4 clients/services or not. We’ll handle the simple case where you have no need to service Kerberos 4 clients or services first.
In this case, you’ll be able to implement a Kerberos 5-based solution with no need for backwards compatibility with Kerberos 4-based systems. All of the KDCs we’ll cover here will be able to handle Kerberos 5 clients, and there will be no need to enable any optional Kerberos 4 compatibility.
On the other hand, if you have to support Kerberos 4 services or clients, you’ll need to plan a bit more carefully to integrate those legacy components into your Kerberos implementation. Typically, in this situation, you’ll want to stick with a Unix-based KDC, since these have built-in support for the older Kerberos 4 protocol.
Your only option when dealing with Kerberos 4 client machines (machines which will be authenticating end users) is to use a KDC with direct support for Kerberos 4. This limits you to Unix-based KDCs. However, if you are supporting a Kerberos 4-based service (such as AFS), you can ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access