By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,847 Members | 2,354 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,847 IT Pros & Developers. It's quick & easy.

Web Services, Digital Certificates, & 403 error code

P: n/a

I have a web service (#1) that contacts another web service (#2) that
requires a digital certificate for access. When#1 calls #2, I'm getting a
HTTP 403 error: Access Forbidden. There are a few other posts on the subject
in this newsgroup but none provide the information I need.

When I use a console application that runs on the same server as #1 to
contact #2, I don't have a problem. I've tried a few options that have not
worked:
1) Having the web service Impersonate the account (through web.config) that
the console application is running under.
2) Installed the certificate in every certificate store imaginable supposing
the ASPNET account does not have access to certain stores.

The OS of the server that hosts #1 is Windows NT and I'm on the 1.1.4322.573
version of the framework. Thanks in advance for all replies.
Nov 23 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a

I've installed winhttpcertcfg and made my certificate accessible to the
ASPNET account. However, this is still not working.

Questions:
--Is there anything on the client side I can do programmatically (I have wse
2.0 installed) to check if I have access to the private key?
--What Do I have to restart (if anything) after I assign permissions to the
private key using winhttpcertcfg?

"Eddie J" wrote:

I have a web service (#1) that contacts another web service (#2) that
requires a digital certificate for access. When#1 calls #2, I'm getting a
HTTP 403 error: Access Forbidden. There are a few other posts on the subject
in this newsgroup but none provide the information I need.

When I use a console application that runs on the same server as #1 to
contact #2, I don't have a problem. I've tried a few options that have not
worked:
1) Having the web service Impersonate the account (through web.config) that
the console application is running under.
2) Installed the certificate in every certificate store imaginable supposing
the ASPNET account does not have access to certain stores.

The OS of the server that hosts #1 is Windows NT and I'm on the 1.1.4322.573
version of the framework. Thanks in advance for all replies.

Nov 23 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.