Good old webservices and SSL



The situation isn't too different, but I still can't find a solution:

1. I have built the web service, my customer is consuming it.
2. Without any certs added to the WS call or cert requiring (in IIS),
the call to the web service works like a charm.
3. Turn on cert requirements and consumer has loaded cert into their
server with winhttpcertcfg and Add it to the WS call it errors.
4. The kicker is that the call drops into catch( e as exception ).
When she checks e.Message it is blank. Stack trace last entry is
ReadResponse().
5. I can only assume that either they've ordered an incorrect cert or
that it was installed correctly, but I don't know how to verify this.
I'm working with them as much as possible, but I don't know what they
need to do to verify.

I had them follow the steps at http://msdn2.microsoft.com/en-us/library/aa302408.aspx.
They say they can't see the certificate listed in the machine store
after using winhttpcertcfg to install. Is this normal? Also, how do
I tell what users have rights to a certificate - this could also be
the issue.

Thanks
sotty

.



Relevant Pages

  • RE: [Full-Disclosure] Openssl proof of concept code? / Neoteris
    ... its own built-in cert and offers it up without solicitation. ... SSL connection with the server with a corrupt cert like that. ... modify a copy of openssl such that it sends a client certificate ... verify error:num=20:unable to get local issuer certificate ...
    (Full-Disclosure)
  • Bad Key
    ... I am working on a demo with WSE using WS-Security. ... This was then installed in the local computer under the Trusted Root ... Then I publish a web service which uses this same cert to encrypt ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Signing with WSE 2.0, no cert on the server side, still works
    ... I am now deploying the web service to a machine other than my dev box ... even before I put the client/calling public key cert on ... receiver doesn't need the cert - can just find the public key there. ... The cert I have signed with on the client side is one created with the ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: certificates for signing documents
    ... but won't verify with is own cert because its root CA ... a public key certificate from a client certificate using makecert ...
    (microsoft.public.platformsdk.security)
  • Re: [WSE 3.0] I need some pointers for using security
    ... After some certificate exporting/importing and fiddling with the ... If I can use only one cert, is there any way to distribute and install ... Do a search for 'Web Service Security Patterns and Practices' on MS website. ...
    (microsoft.public.dotnet.framework.webservices)