Lance Olson

Building distributed/network apps with .NET

Problems accessing the certificate store with .NET Remoting, Web services, or System.Net.HttpWebRequest

We've had a number of questions come up around issues that arise when building .NET client or middle-tier applications that use client certificates.  Most of them stem from the fact that in version 1.0 of the .NET Framework System.Net (and by extension .NET Remoting and XML Web services) were only able to access the current user's certificate store. 

This approach generally works fine for client applications, however, Windows services or code calling a back-end machine from within ASP.NET generally doesn't have a user profile so the current user's certificate store ends up being empty.  There is a workaround for this issue described on MSDN however using a serviced component is not always an option.  Because of this, we've issued an update that will be included in v1.0 SP3 and v1.1 SP1 which checks the user store and the machine store for a given certificate.  This update is described in the following KB article on ms.com. 

In Whidbey, there are managed API's for accessing the store directly which makes dealing with certificates in general much easier.

Comments

Lance Olson said:

We're aiming for Q3 CY04.

-Lance
# June 16, 2004 10:57 PM

Marvin said:

I'm using HTTPWebrequest and x509Certificates to POST to another website, but I'm getting a error saying that my cert does not exist. I installed ASP.net rollup package and still no luck. any ideas?

I do have my certs installed in Local_machine\personal store.
I'm using ASP.net in windows 2003
# August 6, 2004 4:02 AM

HP 125A said:

Fantastic blog post.Really looking forward to read more. Awesome.

# August 14, 2012 8:22 AM

crork said:

kO4mBL Im thankful for the article.Thanks Again. Great.

# September 20, 2012 12:43 PM

loss weight pills said:

g6CsDP Looking forward to reading more. Great blog.Much thanks again. Much obliged.

# January 31, 2013 5:09 PM

epson photo paper said:

Very good post.Much thanks again. Much obliged.

# February 4, 2013 8:38 AM