I have some code that makes a call to a third party web service that is secured using X.509 certification.
If I call the code directly (using a unit test) it works without any problems.
When deployed, this code will be called via a WCF Service. I have added a second unit test that calls the WCF Service, however this fails with a CryptographicException, message "Keyset does not exist" when I call a method on the third party web service.
I presume that this is because my WCF Service will be attempting to call the third party web service using a different user to myself.
Can anyone shed any additional light on this issue?
It will probably be a permissions problem on the certificate.
When running a unit test you are going to be executing those under your own user context, which (depending on what store the client certificate is in) will have access to that certificate's private key.
However if your WCF service is hosted under IIS, or as a Windows Service it's likely it will be running under a service account (Network Service, Local Service or some other restricted account).
You will need to set the appropriate permissions on the private key to allow that service account access to it. MSDN has the details