Home > Articles > Programming > Windows Programming

A .NET Developer's Guide to Windows Security: Understanding Protocol Transition

New to Windows Server 2003, Protocol Transition allows you to establish logon sessions with valid Kerberos credentials for an arbitrary domain user without knowing that user's password. This chapter discusses this new tool and its implications for network security.
This chapter is from the book Protocol transition is a new feature that's been added to Windows Server 2003 domains. Put bluntly, it allows certain designated servers to establish logon sessions with valid Kerberos credentials for an arbitrary domain user without knowing that user's password! As I showed in Item 26, if you're one of these designated servers, you can create a WindowsIdentity for a user, with a real token (Item 16) and logon session (Item 17) behind it. Simply use the WindowsIdentity constructor that takes a single string argument, the user's account name—technically the user principal name (UPN) for the account, which is typically the user's e-mail address.

There are a couple of scenarios where this can be helpful. The first (and the reason for the name "protocol transition") is when you simply can't use Kerberos to authenticate users on the front end of a distributed application. For example, if users are contacting your server over the Internet (without a VPN connection), they likely won't be able to talk to your domain controller to get the tickets necessary to talk to the server because firewalls prevent them from contacting your domain controller (Item 59). This means you'll need to use some other form of authentication, perhaps a client-side certificate in conjunction with SSL, to authenticate your client. In Windows 2000, whatever authentication protocol you chose, once your middle tier authenticated the client, in order to map the user onto a legitimate Windows user account, the middle tier had to know the password for that account in order to establish a logon session and get a token (typically via the Win32 API LogonUser that I discussed in Item 26).

In a perfect world, a user's master key should be known only by that user and her domain authority. But when you need to transition from one authentication protocol (such as SSL) to Kerberos on the back end, the server performing this transition (authenticating the client using SSL in this case and mapping that client onto a Windows account with Kerberos credentials) ends up with a big juicy password database that just screams, "Attack me!" The point of protocol transition is to make it possible for designated servers (think of them as gateways) to be able to perform this service without having to store passwords.

At this point you might be wondering how protocol transition helps. Just because the gateway no longer stores passwords, it can still get a logon for any user it wants (including highly privileged users in the domain). This means an attacker who has compromised the gateway can do the same thing, right? Yes, but protocol transition works hand in hand with the constrained delegation feature in Windows Server 2003 that I discussed in Item 62. In other words, the gateway can't use this feature to obtain tickets for just any servers on the network. Once it logs in the user via protocol transition (without knowing her password, in other words) and impersonates her, when it attempts to use her credentials to talk to other servers on the network, the domain authority only issues tickets for the servers on the gateway's "allow-to-delegate-to" list.

For example, in Figure 63.1, the WEBSERVER gateway will be allowed to log in users without knowing their passwords, but will only be able to use those credentials to talk to SQL Server on a machine called DATASERVER. This sort of constraint wouldn't be possible if WEBSERVER were storing passwords for user accounts. Because we're using protocol transition on WEBSERVER, if that machine is compromised by an attacker, the attacker will find, much to her dismay, that the domain authority simply won't issue tickets for other servers on the network. She won't be able to authenticate with those servers and will be denied access, assuming you've configured your servers to disallow anonymous requests (Item 35)! Sure, the attacker will be able to use a variety of user credentials to get to DATASERVER, but he would have been able to do that (and more) had you stored passwords on WEBSERVER instead. And remember that you should mark highly privileged accounts "sensitive and cannot be delegated" (Item 62), which would restrict the attacker from using those accounts to talk to DATASERVER.

63fig01.gifFigure 63.1 Configuring protocol transition for a gateway

Configuring protocol transition is exactly like configuring constrained delegation, which I cover in Item 64. The only difference is what I've highlighted in Figure 63.1: You must select the option that says "Use any authentication protocol."

Here's another interesting new feature: On any Windows Server 2003 machine that's running in a native Windows Server 2003 domain, you can obtain a token for a domain user without knowing her password. If your server account isn't marked as being trusted to delegate to other servers, you can only use this token to find out what groups the user is in. If your server process is running with the SeTcbPrivilege enabled (SYSTEM is the only security context with this privilege by default, as I discussed in Item 28), you get what's called an impersonation token and you can use it to impersonate and open up local secured objects such as files. Access checks to these resources are made based on the identity in the impersonation token. Without this privilege, you get what's called an identification token, designed only for doing access checks and group lookups. If you try to impersonate using this token, you'll be successful, but if you do anything interesting like try to open a local file, the request will fail.

But even if you get only an identification token, it's still useful because you can use it to see what groups the user is a member of. This has been a really hard problem on Windows 2000, if you can believe it. Recall from Item 20 that group membership lists are decentralized in Windows. Global group memberships are stored in the client's domain, domain local group memberships are stored in the server's domain, and universal group memberships are stored in the Global Catalog. Plus, these domain groups can be nested! Oh, and don't forget local groups, which are stored on individual machines. Trying to discover these group memberships manually is expensive and it's very difficult to get an authoritative answer. The best way to discover the groups for a user is to get a token for her. In the past, however, that required knowing the user's password. With this new feature, you can get a token for a user and get an authoritative list of groups without any hassle. Your server doesn't have to have any special trust to be able to do this (although there's an access check to make sure the server is allowed to read the group memberships for the user).

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020