Kerberos

Use case of kerberos and alternative

**Use Case of Kerberos:**

Kerberos is a network authentication protocol that provides strong authentication for client-server applications by using secret-key cryptography. Its primary use case is to secure communication in a networked environment. Here are some common use cases for Kerberos:

1. **Single Sign-On (SSO):**

   - Kerberos enables Single Sign-On, allowing users to log in once and access various services and applications without the need to re-enter credentials. Once authenticated to the Kerberos Key Distribution Center (KDC), users receive tickets that can be used to access different services.

2. **Secure Authentication for Network Services:**

   - Kerberos is often used to secure authentication for various network services such as file servers, email servers, and web applications. It ensures that only authenticated and authorized users can access these services.

3. **Cross-Realm Authentication:**

   - Kerberos supports cross-realm authentication, allowing users from one Kerberos realm to access services in another realm without the need for separate authentication. This is useful in large organizations with multiple realms.

4. **Mutual Authentication:**

   - Kerberos provides mutual authentication, meaning both the client and the server authenticate each other. This helps prevent various attacks, including man-in-the-middle attacks.

5. **Encryption of Ticket-Granting Tickets (TGTs) and Service Tickets:**

   - Kerberos encrypts TGTs and service tickets to protect them from eavesdropping. This ensures the confidentiality of authentication information during ticket exchange.

6. **Time Sensitivity:**

   - Kerberos tickets have a limited validity period, typically a few hours. This time sensitivity helps mitigate the risk associated with stolen tickets, as they become invalid after a certain period.

**Alternative to Kerberos:**

While Kerberos is a widely used and robust authentication protocol, there are alternative authentication mechanisms, especially in modern computing environments:

1. **OAuth (Open Authorization):**

   - OAuth is an open standard for access delegation commonly used for internet-scale authentication. It allows third-party applications to access resources on behalf of a user without exposing the user's credentials. OAuth is often used in web and mobile applications.

2. **OpenID Connect:**

   - OpenID Connect is an authentication layer built on top of the OAuth 2.0 protocol. It provides identity services on the internet and enables clients to verify the identity of end-users based on the authentication performed by an authorization server.

3. **Security Assertion Markup Language (SAML):**

   - SAML is an XML-based standard for exchanging authentication and authorization data between parties, particularly in a web browser-based Single Sign-On (SSO) context. It is commonly used for identity federation.

4. **JSON Web Tokens (JWT):**

   - JWT is a compact, URL-safe means of representing claims to be transferred between two parties. It is often used for authentication and authorization in web development. JWTs can be signed and optionally encrypted to ensure integrity and confidentiality.

5. **Multi-Factor Authentication (MFA):**

   - MFA involves using multiple methods of authentication to verify the identity of a user. It can include a combination of something the user knows (password), something the user has (smart card or mobile device), and something the user is (biometrics).

Each authentication mechanism has its strengths and weaknesses, and the choice depends on factors such as the specific use case, the nature of the applications, and the security requirements of the system. It's common for organizations to use a combination of authentication methods based on their specific needs.

Kerberos is a computer network authentication protocol, which allows individuals communicating over a non-secure network to prove their identity to one another in a secure manner. It is also a suite of free software published by Massachusetts Institute of Technology (MIT) that implements this protocol. Its designers aimed primarily at a client-server model, and it provides mutual authentication — both the user and the server verify each other's identity. Kerberos protocol messages are protected against eavesdropping and replay attacks.
Kerberos builds on symmetric key cryptography and requires a trusted third party. Extensions to Kerberos can provide for the use of public-key cryptography during certain phases of authentication.

The Kerberos Network Authentication Service

Without knowledge of the identity of an individual requesting an operation, it is often difficult to decide whether the operation should be allowed. Traditional authentication methods are not suitable for use in computer networks where attackers can monitor network traffic and intercept passwords. The use of strong authentication methods that do not disclose passwords is imperative. The Kerberos authentication system supports strong authentication on such networks.

Description

Kerberos uses as its basis the Needham-Schroeder protocol. It makes use of a trusted third party, termed a key distribution center (KDC), which consists of two logically separate parts: an Authentication Server (AS) and a Ticket Granting Server (TGS). Kerberos works on the basis of "tickets" which serve to prove the identity of users.
The KDC maintains a database of secret keys; each entity on the network — whether a client or a server — shares a secret key known only to itself and to the KDC. Knowledge of this key serves to prove an entity's identity. For communication between two entities, the KDC generates a session key which they can use to secure their interactions.

Protocol

The security of the protocol relies heavily on participants maintaining loosely synchronized time and on short-lived assertions of authenticity called Kerberos tickets.
What follows is a simplified description of the protocol. The following abbreviations will be used:

• AS = Authentication Server
• TGS = Ticket Granting Server
• SS = Service Server
• TGT = Ticket Granting Ticket

Briefly, the client authenticates to AS using a long-term shared secret and receives a ticket from the AS. Later the client can use this ticket to get additional tickets for SS without resorting to using the shared secret. These tickets can be used to prove authentication to SS.

User Client-based Logon Steps:

1. A user enters a username and password on the client machine.
2. The client performs a one-way function (hash mostly) on the entered password, and this becomes the secret key of the client/user.

Client Authentication Steps:

1. The client sends a cleartext message to the AS requesting services on behalf of the user. Sample message: "User XYZ would like to request services". Note: Neither the secret key nor the password is sent to the AS.
2. The AS checks to see if the client is in its database. If it is, the AS sends back the following two messages to the client:
• Message A: Client/TGS Session Key encrypted using the secret key of the client/user.
• Message B: Ticket-Granting Ticket (which includes the client ID, client network address, ticket validity period, and the client/TGS session key) encrypted using the secret key of the TGS.
3. Once the client receives messages A and B, it decrypts message A to obtain the Client/TGS Session Key. This session key is used for further communications with TGS. (Note: The client cannot decrypt Message B, as it is encrypted using TGS's secret key.) At this point, the client has enough information to authenticate itself to the TGS.

Client Service Authorization Steps:

1. When requesting services, the client sends the following two messages to the TGS:
• Message C: Composed of the Ticket-Granting Ticket from message B and the ID of the requested service.
• Message D: Authenticator (which is composed of the client ID and the timestamp), encrypted using the Client/TGS Session Key.
2. Upon receiving messages C and D, the TGS retrieves message B out of message C. It decrypts message B using the TGS secret key. This gives it the "client/TGS session key". Using this key, the TGS decrypts message D (Authenticator) and sends the following two messages to the client:
• Message E: Client-to-server ticket (which includes the client ID, client network address, validity period and Client/Server Session Key) encrypted using the service's secret key.
• Message F: Client/server session key encrypted with the Client/TGS Session Key.

Client Service Request Steps:

1. Upon receiving messages E and F from TGS, the client has enough information to authenticate itself to the SS. The client connects to the SS and sends the following two messages:
• Message E from the previous step (the client-to-server ticket, encrypted using service's secret key).
• Message G: a new Authenticator, which includes the client ID, timestamp and is encrypted using client/server session key.

2. The SS decrypts the ticket using its own secret key to retrieve the Client/Server Session Key. Using the session's key, SS decrypts the Authenticator and sends the following message to the client to confirm its true identity and willingness to serve the client:
• Message H: the timestamp found in client's Authenticator plus 1, encrypted using the Client/Server Session Key.
3. The client decrypts the confirmation using the Client/Server Session Key and checks whether the timestamp is correctly updated. If so, then the client can trust the server and can start issuing service requests to the server.
4. The server provides the requested services to the client.

Drawbacks:

• Single point of failure: It requires continuous availability of a central server. When the Kerberos server is down, no one can log in. This can be mitigated by using multiple Kerberos servers and fallback authentication mechanisms.
• Kerberos requires the clocks of the involved hosts to be synchronized. The tickets have a time availability period and if the host clock is not synchronized with the Kerberos server clock, the authentication will fail. The default configuration requires that clock times are no more than 10 minutes apart. In practice, Network Time Protocol daemons are usually used to keep the host clocks synchronized.
• The administration protocol is not standardized and differs between server implementations. Password changes are described in RFC 3244.
• Since the secret keys for all users are stored on the central server, a compromise of that server will compromise all users' secret keys.
• A compromised client will compromise the user's password.

Briefly and approximately, here's how Kerberos works:

1. Suppose you want to access a server on another computer (which you may get to by sending a Telnet or similar login request). You know that this server requires a Kerberos "ticket" before it will honor your request.
2. To get your ticket, you first request authentication from the Authentication Server (AS). The Authentication Server creates a "session key" (which is also an encryption key) basing it on your password (which it can get from your username) and a random value that represents the requested service. The session key is effectively a "ticket-granting ticket."
3. You next send your ticket-granting ticket to a ticket-granting server (TGS). The TGS may be physically the same server as the Authentication Server, but it's now performing a different service. The TGS returns the ticket that can be sent to the server for the requested service.
4. The service either rejects the ticket or accepts it and performs the service.
5. Because the ticket you received from the TGS is time-stamped, it allows you to make additional requests using the same ticket within a certain time period (typically, eight hours) without having to be re-authenticated. Making the ticket valid for a limited time period make it less likely that someone else will be able to use it later.