Async WCF calls with impersonation

by Sven 24. March 2010 10:58

I was playing around with impersonated asynchronous WCF calls and discovered a strange behaviour on the WCF server side: most of the time the identity was the correct impersonated identity but sometimes it was only the client process identity (like 'hostname$'). I was looking at all different configuartion hells of WCF but did not find any solution to fix the problem.

After searching the web I found two interesting posts from Micorosft:

http://msdn.microsoft.com/en-us/library/aa738624.aspx

and

http://support.microsoft.com/?scid=kb%3Ben-us%3B976123&x=10&y=14

The first document stated that I am trying to use an unsupported scenario. The second document says that there is a hotfix available for Vista and Windows Server 2008 (SP2 and higher).

Unfortunately my customer is running Windows 2003 SP2. So there seems to be no way to use async WCF calls with impersonation. Very sad.

Tags:

.NET | ASP.NET | Coding

Comments (2) -

vincent
vincent Netherlands
11/22/2011 2:04:27 PM #

I have the same issue.
My client is calling a service async and is authenticated correctly.
This service is calling another service on the same machine async and this falls back to the app pool (IIS) user. Moving to sync calls fixes this, but will take too much time for the end user.
Did you find a solution?

Reply

Sven
Sven Germany
11/22/2011 3:03:37 PM #

Unfortunately I cannot remember, how I ended up, but a good starting point when you are working with impersonation and kerberos is DelegConfig: www.iis.net/.../default.aspx

HTH, Sven

Reply

Add comment

  Country flag

biuquote
  • Comment
  • Preview
Loading

Page List

My latest Flickr Photos

www.flickr.com

Shared items - Google Reader

Instagram Pictures