The evil tricks of “It Works On My Machine”, in reverse

the following is quite annoying. i am trying to make an authenticated request to a web server. in this instance, we are talking about communication from one iis application to another iis application (the second application is ravendb hosted inside iis).

the part that drives me crazy is that i am getting this error when i am trying to make an authenticated request, but using the exact same code and credentials , from another machine, i can make this work just fine.

it took me a while to figure out that most important part, when running locally, i was running under my own account, when running remotely, the application run under iis account. the really annoying part was that even when running on iis locally, it still worked locally and failed remotely.

it took me even longer to figure out that the local iis was configure to run under my own account as well

once that discovery was made, i was able to figure out what is wrong and implement a work around (run the remote iis site under a custom user name). i know that the actual problem is something relating to permissions on certificate store, but i have no idea how , or, for that matter, which certificate ?

this is plain old http auth, no ssl, client certs, etc. i am assuming that this is raised because we are using windows auth, but i am not sure what is going on here with regards to which certificate should i grant to which user, or even how to do this.

any ideas?