Subscribe to Windows IT Pro

 

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

September 14, 1999 09:40 AM

Kerberos Transitive Trust Examined

Windows IT Pro
InstantDoc ID #7194
Rating: (0)

Suppose Alice has logged on to north.eu108.corp108.com with her user account, and she wants to access a resource on a server in east.na108.corp108.com. The following steps walk you through the Kerberos authentication process in a tree that contains five domains:

  1. Alice uses her ticket-granting ticket (TGT) to try to obtain a ticket from KDC1 for the resource server in the east domain. KDC1 isn't the authority for the resource server's east domain, so KDC1 refers Alice to the domain closest to the target domain that the north domain has a Kerberos trust relationship with. This domain is eu108.
  2. KDC2 refers Alice to KDC3.
  3. KDC3 refers Alice to KDC4.
  4. KDC4 refers Alice to KDC5.
  5. KDC5 is the authority for the east domain, so KDC5 generates a ticket for Alice.
  6. Alice uses the ticket from KDC5 to access the resource server.

If you use Windows 2000's (Win2K's) software development kit (SDK) Klist utility to look at the ticket cache on Alice's machine, you'll find one TGT for each domain, one ticket for Alice's machine (part of the north domain), and one ticket for the resource server.

You can shorten this referral process by creating an explicit trust relationship (i.e., a shortcut trust) between the north and east domains. In this case, Alice will go through the following steps to access the resource located in the east domain:

  1. Alice uses her TGT to try to obtain a ticket from KDC1 for the resource server in the east domain. KDC1 isn't the authority for the resource server's east domain, so KDC1 refers Alice to the domain closest to the target domain that the north domain has a Kerberos trust relationship with. This domain is east.
  2. KDC5 is the authority for the resource server's east domain, so KDC5 generates a ticket for Alice.
  3. Alice uses the ticket from KDC5 to access the resource server.

If you look at the ticket cache on Alice's machine after this process, you'll find only four tickets: one TGT for the north domain, one TGT for the east domain, one ticket for Alice's machine, and one ticket for the resource server. A shortcut trust reduces the interdomain authentication traffic and the number of Kerberos tickets issued.

Related Content:

ARTICLE TOOLS

Comments
    There are no comments to display. Be the first one!
You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

White Papers

Get your Windows 7 deployment off to the right start by implementing PC lockdown. A locked-down environment is easier and cheaper to support since users are less likely to make unnecessary changes to the core system configuration - read more here!

Essential Guides

Is your iSCSI "lossy"? The reality is that most off-the-shelf Ethernet hardware deployed for iSCSI can lose packets, resulting in slow performance or application downtime. Learn how to assess your current iSCSI infrastructure and engineer an advanced iSCSI SAN infrastructure.

Web Seminars

What's the best way to keep your network safe from malware? In this web seminar, security expert Greg Shields suggests an alternative method to the traditional blacklisting approach that is common with anti-virus and anti-malware solutions.

eLearning Series

We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

Subscribe to Windows IT Pro!

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.