Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We work on a server 2003 and server 2008 R2 enviroment.
I'm familiar with the basic usage of the Kerberos protocol where the protocol authenticates a client when he tries to use a shared resource (server, folder, printer, etc.).
We have three distinct and independent .NET applications that we develop inhouse (app A, app B & app C) but they need to communicate for a given reason (A recieves messages only from B and C and C recieves messages only from B).
Is it possible to configure the Kerberos services to authenticate messages/request between two .NET apps ? (Instead of a user-server authentication, we will have an application-application authentication)

share|improve this question
up vote 0 down vote accepted

Usually applications run under some identity, either a user or computer. Those security principals can be authenticated against a kerberos domain/realm. Further, authorization may be determined by the entries in the pac (privilege attribute certificate). If the app does not run under a domain user or computer identity, kerberos may not be of much use.

One option in this scenario may be certificate authentication.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.